From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2 v3] arch: allow passing compile flags (branch yem/arc-atomic)
Date: Sat, 20 Jul 2019 15:38:40 +0200 [thread overview]
Message-ID: <20190720153840.62587aff@windsurf> (raw)
In-Reply-To: <20190718225740.509c41f1@windsurf>
On Thu, 18 Jul 2019 22:57:40 +0200
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Thu, 18 Jul 2019 22:52:46 +0200
> "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
>
> > Yann E. MORIN (2):
> > toolchain: allow architectures to enforce compilation flags
> > arch/arc: always needs -matomic with atomix extensions
>
> Thanks, I've applied the series. I extended the commit log of the
> second patch, because it was really terse.
>
> Following this, I believe it would make sense to move the two remaining
> uses of TARGET_ABI in package/Makefile.in to the appropriate arch/
> file, and drop TARGET_ABI entirely. Indeed, those ABI options are
> really mandatory, if they don't get passed to the cross-compiler,
> things are going to be clearly wrong.
Also, in relation to this, I think we could probably revert commit
18855d79e2e86dc646182bd6f4861c491a05c624 one the TARGET_ABI flags are
encoded into the compiler wrapper.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-07-20 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 20:52 [Buildroot] [PATCH 0/2 v3] arch: allow passing compile flags (branch yem/arc-atomic) Yann E. MORIN
2019-07-18 20:52 ` [Buildroot] [PATCH 1/2 v3] toolchain: allow architectures to enforce compilation flags Yann E. MORIN
2019-07-18 20:52 ` [Buildroot] [PATCH 2/2 v3] arch/arc: always needs -matomic with atomix extensions Yann E. MORIN
2019-07-18 20:57 ` [Buildroot] [PATCH 0/2 v3] arch: allow passing compile flags (branch yem/arc-atomic) Thomas Petazzoni
2019-07-20 13:38 ` Thomas Petazzoni [this message]
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=20190720153840.62587aff@windsurf \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox