From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ext-toolchain: Automatically set -m64 if the architecture is x86_64
Date: Wed, 14 Mar 2012 23:23:30 +0100 [thread overview]
Message-ID: <20120314232330.540d0ee2@skate> (raw)
In-Reply-To: <201203132255.09448.arnout@mind.be>
Le Tue, 13 Mar 2012 22:55:08 +0100,
Arnout Vandecappelle <arnout@mind.be> a ?crit :
> > I disagree with this change. If you select "i386" or "i486" as the
> > Target Architecture Variant, then this Sourcery CodeBench toolchain
> > will not work: it only has libc variants for Pentium 4, Atom, Xeon and
> > Core 2, so if you try to use it on something older than Pentium 4, it
> > might use nonexistent instructions.
>
> Ah, I hadn't thought of the pre-P4 variants.
>
> > Can you explain why you made this change, or revert it?
>
> My customer, after reading this help text, thought that it wouldn't work
> on his Athlon processor. And the same would go for Celerons and whatnot.
> So instead of enumerating all of them, I thought I'd simplify the help
> text.
Well, I think it's quite important to know which multilib variants are
available. Maybe we could make the wording a bit different by saying
that such and such multilib variant is for processor XXX or later ?
> And the second part of the patch removed the necessity of the
> -m64 option so that didn't need to be mentioned anymore either.
Maybe, but we have the same text for other multilib variants of all
toolchains, many of which require special options.
> > I don't agree here. -m64 is not an option that exists for all
> > 64-bits architectures. For example, it does not exist on MIPS. -m64 is
> > part of the architecture-specific options of gcc, so your change should
> > rather be:
> >
> > ifeq ($(BR2_x86_64),y)
> > TOOLCHAIN_EXTERNAL_CFLAGS += -m64
> > TOOLCHAIN_EXTERNAL_WRAPPER_ARGS += -DBR_64
> > endif
>
> OK.
Can you respin the patch with this?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-03-14 22:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 18:04 [Buildroot] [PATCH] ext-toolchain: Automatically set -m64 if the architecture is x86_64 Arnout Vandecappelle
2012-01-23 21:36 ` Thomas Petazzoni
2012-03-05 10:12 ` Thomas Petazzoni
2012-03-13 21:55 ` Arnout Vandecappelle
2012-03-14 22:23 ` Thomas Petazzoni [this message]
2012-03-13 22:30 ` [Buildroot] [PATCHv2] " Arnout Vandecappelle
2012-03-14 22:25 ` Thomas Petazzoni
2012-03-14 23:01 ` Peter Korsgaard
2012-03-15 8:17 ` Arnout Vandecappelle
2012-03-15 9:44 ` Peter Korsgaard
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=20120314232330.540d0ee2@skate \
--to=thomas.petazzoni@free-electrons.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