This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH][4/4][v2] RPO-style value-numbering for FRE/PRE
- From: John David Anglin <dave at hiauly3 dot hia dot nrc dot ca>
- To: Gerald Pfeifer <gerald at pfeifer dot com>
- Cc: Richard Biener <rguenther at suse dot de>, gcc-patches at gcc dot gnu dot org, dave dot anglin at bell dot net
- Date: Wed, 12 Sep 2018 15:23:41 -0400
- Subject: Re: [PATCH][4/4][v2] RPO-style value-numbering for FRE/PRE
- References: <alpine.LSU.2.20.1808241317570.16707@zhemvz.fhfr.qr> <alpine.LSU.2.21.1809042357180.6216@anthias.pfeifer.com>
On Wed, Sep 05, 2018 at 12:12:39AM +0200, Gerald Pfeifer wrote:
> On Fri, 24 Aug 2018, Richard Biener wrote:
> > Comments are still welcome - I've re-bootstrapped and tested the series
> > on x86_64-unknown-linux-gnu for all languages and will talk about
> > this work@the Cauldron in more detail.
>
> Is there any chance you can test this on i586 as well?
>
> Since around that commit (August 27th) my i586 builds are failing
> with something like
>
> during GIMPLE pass: pre
> cp-demangle.c: In function ?d_print_comp?:
> cp-demangle.c:5711:1: internal compiler error: Segmentation fault
> 5711 | d_print_comp (struct d_print_info *dpi, int options,
> | ^~~~~~~~~~~~
>
> when doing a regular bootstrap on i586-unknown-freebsd10.4 (with
> clang 3.4.1 as system compiler).
>
> Alas, when I add -save-temps, the internal compiler error goes away,
> and the backtrace using gdb installed on that system I share isn't
> very useful, either. (When I replace cp-demangle.c by cp-demangle.i
> in the invocation the error also disppears.)
>
> On the other hand, this ICE has been consistent across a week of
> daily builds now.
I see the same thing on hppa2.0w-hp-hpux11.11. I did a regression search
and 263875 is the culprit. I've seen segmentation faults in cp-demangle.c
and macro.c. Again, this is tough to debug.
Dave