From: David Edelsohn <dje.gcc@gmail.com>
To: Jason Merrill <jason@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: C++ PATCH to integrate c++-delayed-folding branch
Date: Tue, 17 Nov 2015 14:52:00 -0000 [thread overview]
Message-ID: <CAGWvny=JLY=RxrGvkKJtnD2D7GVLEjwS0MvLq_2BcjXffBifKA@mail.gmail.com> (raw)
In-Reply-To: <564AA34F.8090901@redhat.com>
On Mon, Nov 16, 2015 at 10:47 PM, Jason Merrill <jason@redhat.com> wrote:
> On 11/16/2015 09:39 PM, David Edelsohn wrote:
>>
>> The PPC port seems to be bootstrapping again, but I'm not sure why.
>> Mike Meissner's patch only should have affected long double.
>
>
>> It's hard to know if there is a latent bug that has gone back into hiding.
>
>
> The problem was twofold:
>
> 1) VSX_L included IFmode, but VSa didn't, so expanding various patterns over
> VSX_L generated an IFmode insn that still had <VSa> scattered around.
> Mike's patch fixed this.
>
> 2) The delayed folding merge changed
>
> __builtin_constant_p (non-constant-expr && false)
>
> to be false because the operand is not a C++ constant expression. Previously
> we had seen that the IFmode insn was inactive because its test was known to
> be false, but with this change we needed to evaluate its test at runtime, so
> we had to parse the insn itself, so we ran into problem #1.
>
> I have a patch to fix the __builtin_constant_p regression which I will be
> checking in shortly.
Thanks for debugging and fixing this!
- David
next prev parent reply other threads:[~2015-11-17 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 4:46 David Edelsohn
2015-11-14 6:47 ` Jason Merrill
2015-11-17 2:39 ` David Edelsohn
2015-11-17 3:47 ` Jason Merrill
2015-11-17 14:52 ` David Edelsohn [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-14 0:07 Jason Merrill
2015-11-16 23:13 ` Joseph Myers
2015-11-16 23:15 ` Jeff Law
2015-11-17 9:10 ` Andreas Schwab
2015-11-17 13:49 ` Jason Merrill
2015-11-17 13:57 ` Andreas Schwab
2015-11-17 14:09 ` Alan Lawrence
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='CAGWvny=JLY=RxrGvkKJtnD2D7GVLEjwS0MvLq_2BcjXffBifKA@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.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).