From: Richard Biener <richard.guenther@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Ramana Radhakrishnan <ramana.radhakrishnan@foss.arm.com>,
Andreas Tobler <andreast@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7
Date: Tue, 24 May 2016 09:01:00 -0000 [thread overview]
Message-ID: <CAFiYyc04WYGawMfhqXT+RqZer0XatbJ=gXwabfDT9HDHU=HVvQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1605232342040.2874@anthias.pfeifer.com>
On Tue, May 24, 2016 at 12:20 AM, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> On Mon, 23 May 2016, Richard Biener wrote:
>> So I propose to demote -freebsd to secondary and use
>> i686-unknown-freebsd (or x86_64-unknown-freebsd?).
>>
>> Gerald, Andreas, can you comment on both issues? Esp. i386
>> is putting quite some burden on libstdc++ and atomics support
>> for example.
>
> As Jeff noted, i386 actually is the "marketing" name used for the
> platform, GCC has been defaulting to i486 for ages, and I upgraded
> to i586 last year:
>
> 2015-11-15 Gerald Pfeifer <gerald@pfeifer.com>
>
> * config/i386/freebsd.h (SUBTARGET32_DEFAULT_CPU): Change to i586.
> Remove support for FreeBSD 5 and earlier.
>
> And, yes, the system compiler on current versions of FreeBSD is
> LLVM (for most platforms including x86). There is still a fair
> user base, though.
>
> Given the above, do you still see a desire to make this change?
Can we update to a non-marketing name then, like i586-unknown-freebsd please?
config.gcc accepts i[34567]86-*-freebsd*. It at least confused me.
Richard.
> Gerald
next prev parent reply other threads:[~2016-05-24 9:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 9:17 Ramana Radhakrishnan
2016-05-23 9:26 ` Richard Biener
2016-05-23 15:47 ` Jeff Law
2016-05-23 22:21 ` Gerald Pfeifer
2016-05-24 9:01 ` Richard Biener [this message]
2017-03-04 16:40 ` i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7) Gerald Pfeifer
2017-03-07 16:34 ` i386-unknown-freebsd -> i586-unknown-freebsd Jeff Law
2017-03-07 20:01 ` Updating config.guess (was: i386-unknown-freebsd -> i586-unknown-freebsd) Gerald Pfeifer
2017-03-13 15:33 ` Updating config.guess Jeff Law
2017-03-18 18:23 ` Gerald Pfeifer
2017-03-04 16:45 ` i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7) Gerald Pfeifer
2017-03-07 16:33 ` i386-unknown-freebsd -> i586-unknown-freebsd Jeff Law
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='CAFiYyc04WYGawMfhqXT+RqZer0XatbJ=gXwabfDT9HDHU=HVvQ@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=andreast@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=ramana.radhakrishnan@foss.arm.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).