From: Segher Boessenkool <segher@kernel.crashing.org>
To: George Spelvin <lkml@sdf.org>
Cc: heiko.carstens@de.ibm.com, linux-s390@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-mips@vger.kernel.org,
linux-alpha@vger.kernel.org
Subject: Re: CONFIG_ARCH_SUPPORTS_INT128: Why not mips, s390, powerpc, and alpha?
Date: Sat, 30 Mar 2019 19:30:21 -0500 [thread overview]
Message-ID: <20190331003020.GO3969@gate.crashing.org> (raw)
In-Reply-To: <201903301030.x2UAUNOg026448@sdf.org>
On Sat, Mar 30, 2019 at 10:30:23AM +0000, George Spelvin wrote:
> For s390, that was added on 24 March 2017 by
> https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=246457
> which is part of GCC 7.
>
> It also only applies to TARGET_ARCH12, which I am guessing
> corresponds to HAVE_MARCH_ZEC12_FEATURES.
zEC12 is arch10, while z14 is arch12. See
https://sourceware.org/binutils/docs-2.32/as/s390-Options.html#s390-Options
for example; it lists the correspondences, and states "The processor names
starting with arch refer to the edition number in the Principle of
Operations manual. They can be used as alternate processor names and have
been added for compatibility with the IBM XL compiler."
Newer GCC does not use the somewhat confusing TARGET_ARCH12 name anymore;
see https://gcc.gnu.org/r264796 .
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: George Spelvin <lkml@sdf.org>
Cc: linux-s390@vger.kernel.org, linux-alpha@vger.kernel.org,
heiko.carstens@de.ibm.com, linuxppc-dev@lists.ozlabs.org,
linux-mips@vger.kernel.org
Subject: Re: CONFIG_ARCH_SUPPORTS_INT128: Why not mips, s390, powerpc, and alpha?
Date: Sat, 30 Mar 2019 19:30:21 -0500 [thread overview]
Message-ID: <20190331003020.GO3969@gate.crashing.org> (raw)
In-Reply-To: <201903301030.x2UAUNOg026448@sdf.org>
On Sat, Mar 30, 2019 at 10:30:23AM +0000, George Spelvin wrote:
> For s390, that was added on 24 March 2017 by
> https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=246457
> which is part of GCC 7.
>
> It also only applies to TARGET_ARCH12, which I am guessing
> corresponds to HAVE_MARCH_ZEC12_FEATURES.
zEC12 is arch10, while z14 is arch12. See
https://sourceware.org/binutils/docs-2.32/as/s390-Options.html#s390-Options
for example; it lists the correspondences, and states "The processor names
starting with arch refer to the edition number in the Principle of
Operations manual. They can be used as alternate processor names and have
been added for compatibility with the IBM XL compiler."
Newer GCC does not use the somewhat confusing TARGET_ARCH12 name anymore;
see https://gcc.gnu.org/r264796 .
Segher
next prev parent reply other threads:[~2019-03-31 0:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 13:07 CONFIG_ARCH_SUPPORTS_INT128: Why not mips, s390, powerpc, and alpha? George Spelvin
2019-03-29 20:00 ` Michael Cree
2019-03-29 20:00 ` Michael Cree
2019-03-30 23:14 ` Segher Boessenkool
2019-03-29 20:25 ` Segher Boessenkool
2019-03-29 20:25 ` Segher Boessenkool
2019-03-30 11:28 ` George Spelvin
2019-03-30 11:28 ` George Spelvin
2019-03-30 23:52 ` Segher Boessenkool
2019-03-30 23:52 ` Segher Boessenkool
2019-03-30 8:43 ` Heiko Carstens
2019-03-30 8:43 ` Heiko Carstens
2019-03-30 10:30 ` George Spelvin
2019-03-30 10:30 ` George Spelvin
2019-03-30 13:00 ` George Spelvin
2019-03-30 13:00 ` George Spelvin
2019-03-31 0:30 ` Segher Boessenkool [this message]
2019-03-31 0:30 ` Segher Boessenkool
2019-03-31 9:23 ` George Spelvin
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=20190331003020.GO3969@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkml@sdf.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.