From: Segher Boessenkool <segher@kernel.crashing.org>
To: Peter Bergner <bergner@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Michael Meissner <meissner@linux.ibm.com>
Subject: Re: [PATCH, rs6000] Fix PR87496: ICE in aggregate_value_p at gcc/function.c:2046
Date: Tue, 04 Dec 2018 22:54:00 -0000 [thread overview]
Message-ID: <20181204225358.GM3803@gate.crashing.org> (raw)
In-Reply-To: <7abf394f-35a8-08b6-4f7d-f00fd6663930@linux.ibm.com>
On Tue, Dec 04, 2018 at 01:42:52PM -0600, Peter Bergner wrote:
> On 11/28/18 3:27 PM, Peter Bergner wrote:
> > gcc/
> > PR target/87496
> > * config/rs6000/rs6000.c (rs6000_option_override_internal): Disallow
> > -mabi=ieeelongdouble without both -mpopcntd and -mvsx.
>
> So this "fix" ended up accidentally disallowing -mabi=ibmlongdouble as well,
> which is wrong. I need to look at not only whether the variable
> global_options_set.x_rs6000_ieeequad is set, which tells us whether we
> used -mabi={ibm,ieee}longdouble, but whether we actually enabled ieee128.
> The patch below fixes that oversight. As we talked offline, we also should
> not allow either -mabi={ibm,ieee}longdouble with -mlong-double-64, since
> they are conflicting options. I have added code to test for that as well.
> I have also added extra test cases to test for those.
Okay, so you make -mabi={ibm,ieee}longdouble be valid options only if
there is -mlong-double-128. Could you add that to the documentation then
please?
> Is this ok for mainline once bootstrap and regtesting come back clean?
Okay with that documentation added and if it tests okay, yes. Thanks!
> Since I backported the earlier fix to GCC8, I'd like to backport this
> there too.
Okay for there too.
Segher
> gcc/
> PR target/87496
> * config/rs6000/rs6000.c (rs6000_option_override_internal): Disallow
> -mabi=ieeelongdouble and -mabi=ibmlongdouble without -mlong-double-128.
> Do not error for -mabi=ibmlongdouble and no ISA 2.06 support.
>
> gcc/testsuite/
> PR target/87496
> * gcc.target/powerpc/pr87496.c: Rename from this...
> * gcc.target/powerpc/pr87496-1.c: ...to this. Update comment.
> * gcc.target/powerpc/pr87496-2.c: New test.
> * gcc.target/powerpc/pr87496-3.c: New test.
next prev parent reply other threads:[~2018-12-04 22:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 21:27 Peter Bergner
2018-11-29 2:11 ` Peter Bergner
2018-11-29 17:26 ` Segher Boessenkool
2018-11-29 19:31 ` Peter Bergner
2018-11-29 23:40 ` Peter Bergner
2018-12-04 19:43 ` Peter Bergner
2018-12-04 22:54 ` Segher Boessenkool [this message]
2018-12-07 17:38 ` Peter Bergner
2018-12-12 20:00 ` Peter Bergner
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=20181204225358.GM3803@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@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).