From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux-tools/perf: Respect TARGET_CFLAGS
Date: Wed, 8 May 2019 16:31:27 +0200 [thread overview]
Message-ID: <20190508143127.GD31209@scaer> (raw)
In-Reply-To: <CY4PR1201MB012025B382EBDE4883CA80B8A1320@CY4PR1201MB0120.namprd12.prod.outlook.com>
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.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-05-08 14:31 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 [this message]
2019-05-08 14:54 ` [Buildroot] [arc-buildroot] " Alexey Brodkin
2019-05-09 18:12 ` 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=20190508143127.GD31209@scaer \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox