public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][4/4][v2] RPO-style value-numbering for FRE/PRE
Date: Wed, 05 Sep 2018 06:59:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.20.1809050858090.16707@zhemvz.fhfr.qr> (raw)
In-Reply-To: <alpine.LSU.2.21.1809042357180.6216@anthias.pfeifer.com>

[-- Attachment #1: Type: text/plain, Size: 2305 bytes --]

On Wed, 5 Sep 2018, 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 at the Cauldron in more detail.
> 
> Is there any chance you can test this on i586 as well?

Sounds similar to PR87134?  I do see successful bootstraps on i?86-linux
on gcc-testresults though.

> 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.

Any help with tracking this down appreciated ...

Richard.

> Gerald
> 
> /scratch/tmp/gerald/OBJ-0904-1640/./gcc/xgcc -B/scratch/tmp/gerald/OBJ-0904-1640/./gcc/ -B/home/gerald/gcc-ref10-i386/i586-unknown-freebsd10.4/bin/ 
> -B/home/gerald/gcc-ref10-i386/i586-unknown-freebsd10.4/lib/ -isystem 
> /home/gerald/gcc-ref10-i386/i586-unknown-freebsd10.4/include -isystem 
> /home/gerald/gcc-ref10-i386/i586-unknown-freebsd10.4/sys-include -fno-checking -DHAVE_CONFIG_H -I.. 
> -I/scratch/tmp/gerald/GCC-HEAD/libstdc++-v3/../libiberty 
> -I/scratch/tmp/gerald/GCC-HEAD/libstdc++-v3/../include -D_GLIBCXX_SHARED 
> -I/scratch/tmp/gerald/OBJ-0904-1640/i586-unknown-freebsd10.4/libstdc++-v3/include/i586-unknown-freebsd10.4 
> -I/scratch/tmp/gerald/OBJ-0904-1640/i586-unknown-freebsd10.4/libstdc++-v3/include 
> -I/scratch/tmp/gerald/GCC-HEAD/libstdc++-v3/libsupc++ -g -O2 -DIN_GLIBCPP_V3 -Wno-error 
> -c cp-demangle.c  -fPIC -DPIC -o cp-demangle.o

-- 
Richard Biener <rguenther@suse.de>
SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

  parent reply	other threads:[~2018-09-05  6:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24 11:24 Richard Biener
2018-09-04 22:12 ` Gerald Pfeifer
2018-09-04 22:20   ` Jeff Law
2018-09-05  7:46     ` Gerald Pfeifer
2018-09-05  7:50       ` Richard Biener
2018-09-10 11:04         ` Martin Liška
2018-09-10 12:19           ` Gerald Pfeifer
2018-09-10 12:41             ` Martin Liška
2018-09-13  7:17               ` Gerald Pfeifer
2018-09-13  7:33                 ` Richard Biener
2018-09-13  8:42                   ` Richard Biener
2018-09-13  9:25                     ` Richard Biener
2018-09-14 18:23                       ` Gerald Pfeifer
2018-09-05  6:59   ` Richard Biener [this message]
2018-09-12 19:38   ` John David Anglin

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=alpine.LSU.2.20.1809050858090.16707@zhemvz.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.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).