From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2 v2] arch/arc: always needs -matomic with atomix extensions
Date: Sun, 14 Jul 2019 16:45:43 +0200 [thread overview]
Message-ID: <20190714144543.GC25166@scaer> (raw)
In-Reply-To: <8d0887d8b7c56dd2b92314886f35bdaa7d57894d.1563114574.git.yann.morin.1998@free.fr>
All,
On 2019-07-14 16:29 +0200, Yann E. MORIN spake thusly:
> As reported by Alexey:
> https://patchwork.ozlabs.org/patch/1087480/
> https://patchwork.ozlabs.org/patch/1087471/
>
> Reported-by: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Cc: Arnout Vandecappelle <arnout@mind.be>
>
> ---
> Changes v1 -> v2:
> - move the condition out of package/Makefile.in (Alexey)
> ---
> arch/arch.mk.arc | 4 ++++
> package/Makefile.in | 4 ----
> 2 files changed, 4 insertions(+), 4 deletions(-)
> create mode 100644 arch/arch.mk.arc
>
> diff --git a/arch/arch.mk.arc b/arch/arch.mk.arc
> new file mode 100644
> index 0000000000..559216a733
> --- /dev/null
> +++ b/arch/arch.mk.arc
> @@ -0,0 +1,4 @@
> +# -matomic is always required when the ARC core has the atomic extensions
> +ifeq ($(BR2_arc)$(BR2_ARC_ATOMIC_EXT),y)
Damned, I forgot to git-commit-amend... :-( It should be 'yy' rather
than a single ...
Regards,
Yann E. MORIN.
> +ARCH_TOOLCHAIN_WRAPPER_OPTS = -matomic
> +endif
> diff --git a/package/Makefile.in b/package/Makefile.in
> index f05b9cc3aa..0a7899c852 100644
> --- a/package/Makefile.in
> +++ b/package/Makefile.in
> @@ -112,10 +112,6 @@ ifeq ($(BR2_xtensa),y)
> TARGET_ABI += -mlongcalls -mauto-litpools
> endif
>
> -ifeq ($(BR2_arc)$(BR2_ARC_ATOMIC_EXT),yy)
> -TARGET_ABI += -matomic
> -endif
> -
> STAGING_SUBDIR = $(GNU_TARGET_NAME)/sysroot
> STAGING_DIR = $(HOST_DIR)/$(STAGING_SUBDIR)
>
> --
> 2.20.1
>
--
.-----------------.--------------------.------------------.--------------------.
| 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-07-14 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 14:29 [Buildroot] [PATCH 0/2 v2] arch: allow passing compile flags (branch yem/arc-atomic) Yann E. MORIN
2019-07-14 14:29 ` [Buildroot] [PATCH 1/2 v2] toolchain: allow architectures to enforce compilation flags Yann E. MORIN
2019-07-14 14:29 ` [Buildroot] [PATCH 2/2 v2] arch/arc: always needs -matomic with atomix extensions Yann E. MORIN
2019-07-14 14:45 ` Yann E. MORIN [this message]
2019-07-16 17:52 ` [Buildroot] [PATCH 0/2 v2] arch: allow passing compile flags (branch yem/arc-atomic) Alexey Brodkin
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=20190714144543.GC25166@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