From: Richard Biener <richard.guenther@gmail.com>
To: Ramana Radhakrishnan <ramana.radhakrishnan@foss.arm.com>,
Gerald Pfeifer <gp@suse.com>,
Andreas Tobler <andreast@gcc.gnu.org>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7
Date: Mon, 23 May 2016 09:26:00 -0000 [thread overview]
Message-ID: <CAFiYyc2xYL0116_ucua3kkHDAE9P7mpurTVJoWL8QOsqcdTa+Q@mail.gmail.com> (raw)
In-Reply-To: <5742CA86.10200@foss.arm.com>
On Mon, May 23, 2016 at 11:16 AM, Ramana Radhakrishnan
<ramana.radhakrishnan@foss.arm.com> wrote:
> Hi,
>
> The Steering Committee has decided to add aarch64-none-linux-gnu as a primary platform for GCC-7. This reflects the increasing popularity of the port and the increased general availability of hardware. I also took the opportunity of creating a GCC-7 criteria page at the same time.
>
> Applied.
Sorry to hijack the thread but I continue to notice that we have
i386-unknown-freebsd as a primary target. I notice here
the 'i386' (the only primary target still explicitely listing that
sub-target) and the fact that freebsd switched to LLVM as
far as I know.
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.
Thanks,
Richard.
> Thanks,
> Ramana
next prev parent reply other threads:[~2016-05-23 9:26 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 [this message]
2016-05-23 15:47 ` Jeff Law
2016-05-23 22:21 ` Gerald Pfeifer
2016-05-24 9:01 ` Richard Biener
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=CAFiYyc2xYL0116_ucua3kkHDAE9P7mpurTVJoWL8QOsqcdTa+Q@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=andreast@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gp@suse.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).