From: Segher Boessenkool <segher@kernel.crashing.org>
To: Bill Schmidt <wschmidt@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] rs6000: Add target supports for "future" system
Date: Thu, 30 May 2019 19:32:00 -0000 [thread overview]
Message-ID: <20190530192627.GA31586@gate.crashing.org> (raw)
In-Reply-To: <13012539-5f8a-312b-715c-aa8d3fd46576@linux.ibm.com>
On Wed, May 29, 2019 at 10:52:38PM -0500, Bill Schmidt wrote:
> * lib/target-supports.exp (check_powerpc_future_hw_available):
> New.
That fits on one line just fine?
> +# Return 1 if this is a PowerPC target supporting -mfuture.
> +# Limit this to 64-bit linux systems for now until other
> +# targets support FUTURE.
> +
> +proc check_effective_target_powerpc_future_ok { } {
> + if { ([istarget powerpc64*-*-linux*]) } {
It should be limited to powerpc64le-*-linux, or at least to ELFv2, right?
Not that that should matter at all: you pass -mfuture, and the compiler
will not allow that on unsupported configurations anyway (right? :-) )
But, okay for trunk. Thanks!
Segher
prev parent reply other threads:[~2019-05-30 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 3:55 Bill Schmidt
2019-05-30 19:32 ` Segher Boessenkool [this message]
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=20190530192627.GA31586@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=wschmidt@linux.ibm.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).