From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [arc-buildroot] [PATCH] linux-tools/perf: Respect TARGET_CFLAGS
Date: Wed, 8 May 2019 14:54:13 +0000 [thread overview]
Message-ID: <CY4PR1201MB01208EC953B8DFBB678E8D44A1320@CY4PR1201MB0120.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20190508143127.GD31209@scaer>
Hi Yann,
> -----Original Message-----
> From: Yann E. MORIN <yann.morin.1998@free.fr>
> Sent: Wednesday, May 8, 2019 5:31 PM
> To: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>; buildroot at busybox.net; ARC Buildroot mailing list
> <arc-buildroot@synopsys.com>; Arnout Vandecappelle <arnout@mind.be>
> Subject: Re: [arc-buildroot] [Buildroot] [PATCH] linux-tools/perf: Respect TARGET_CFLAGS
>
> Alexey, All,
>
> On 2019-05-08 13:19 +0000, Alexey Brodkin spake thusly:
> > From: Yann E. MORIN <yann.morin.1998@gmail.com> On Behalf Of Yann E. MORIN
> [--SNIP--]
> > > I'm not too fond of this, but what about the following:
> > >
> > > diff --git a/arch/arch.mk.arc b/arch/arch.mk.arc
> > > new file mode 100644
> > > index 0000000000..83503841b6
> > > --- /dev/null
> > > +++ b/arch/arch.mk.arc
> > > @@ -0,0 +1,3 @@
> > > +ifeq ($(BR2_arcle),y)
> > > +ARCH_TOOLCHAIN_WRAPPER_OPTS = -matomic
> > > +endif
> > > diff --git a/toolchain/toolchain-wrapper.mk
> > > b/toolchain/toolchain-wrapper.mk
> > > index ca66fa7ba4..8f872506ec 100644
> > > --- a/toolchain/toolchain-wrapper.mk
> > > +++ b/toolchain/toolchain-wrapper.mk
> > > @@ -17,6 +17,7 @@ TOOLCHAIN_WRAPPER_ARGS =
> > > $($(PKG)_TOOLCHAIN_WRAPPER_ARGS)
> > > TOOLCHAIN_WRAPPER_ARGS += -DBR_SYSROOT='"$(STAGING_SUBDIR)"'
> > >
> > > TOOLCHAIN_WRAPPER_OPTS = \
> > > + $(ARCH_TOOLCHAIN_WRAPPER_OPTS) \
> > > $(call qstrip,$(BR2_SSP_OPTION)) \
> > > $(call qstrip,$(BR2_TARGET_OPTIMIZATION))
> >
> > That looks good to me with only one change: prefer generic "BR2_arc"
> > instead of little-endian only "BR2_arcle".
>
> Yes, of course, it was just a quicky to demo what I was thinking...
>
> > Care to send-out a patch?
>
> Aw... But *you* are the arc guy! ;-)
>
> OK, will do.
I'm all for sending it myself but it will be like I'm stealing
your nice idea - nothing more that that.
Want me to do that instead?
-Alexey
next prev parent reply other threads:[~2019-05-08 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 9:39 [Buildroot] [PATCH] linux-tools/perf: Respect TARGET_CFLAGS Alexey Brodkin
2019-04-18 9:43 ` Thomas Petazzoni
2019-04-21 7:36 ` Arnout Vandecappelle
2019-04-26 6:30 ` Alexey Brodkin
2019-04-27 17:39 ` Arnout Vandecappelle
2019-04-27 17:56 ` Yann E. MORIN
2019-05-08 13:19 ` Alexey Brodkin
2019-05-08 14:31 ` Yann E. MORIN
2019-05-08 14:54 ` Alexey Brodkin [this message]
2019-05-09 18:12 ` [Buildroot] [arc-buildroot] " Yann E. MORIN
2019-07-18 20:58 ` [Buildroot] " Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CY4PR1201MB01208EC953B8DFBB678E8D44A1320@CY4PR1201MB0120.namprd12.prod.outlook.com \
--to=alexey.brodkin@synopsys.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.