public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* Internal Compiler Error (ICE) building gcc 8.3.0 on ppc64 Linux
@ 2019-03-26  1:58 Brian Groose
  2019-03-26  6:13 ` Segher Boessenkool
  2019-03-28  3:19 ` Peter Bergner
  0 siblings, 2 replies; 5+ messages in thread
From: Brian Groose @ 2019-03-26  1:58 UTC (permalink / raw)
  To: gcc-help

I am trying to build gcc 8.3.0 on linux ppc64.  I have successfully
built 5.3.0 without issue on this machine.  When I build 8.3.0,
however, I hit this error:

/root/gcc/act-gcc-8.3.0-sandbox/build-gcc/./gcc/xgcc
-B/root/gcc/act-gcc-8.3.0-sandbox/build-gcc/./gcc/
-B/opt/act-gcc-8.3.0/powerpc64-unknown-linux-gnu/bin/
-B/opt/act-gcc-8.3.0/powerpc64-unknown-linux-gnu/lib/ -isystem
/opt/act-gcc-8.3.0/powerpc64-unknown-linux-gnu/include -isystem
/opt/act-gcc-8.3.0/powerpc64-unknown-linux-gnu/sys-include    -g -O2
-O2  -g -O2 -DIN_GCC    -W -Wall -Wwrite-strings -Wcast-qual
-Wno-format -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition  -isystem ./include   -fPIC -mlong-double-128
-mno-minimal-toc -g -DIN_LIBGCC2 -fbuilding-libgcc
-fno-stack-protector   -fPIC -mlong-double-128 -mno-minimal-toc -I.
-I. -I../.././gcc -I/root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc
-I/root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/.
-I/root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/../gcc
-I/root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/../include
-I/root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/../libdecnumber/dpd
-I/root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/../libdecnumber
-DHAVE_CC_TLS  -o _muldi3.o -MT _muldi3.o -MD -MP -MF _muldi3.dep
-DL_muldi3 -c /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/libgcc2.c
-fvisibility=hidden -DHIDE_EXPORTS
during GIMPLE pass: store-merging
In file included from
/root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/libgcc2.c:56:
/root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/libgcc2.c: In
function ‘__multi3’:
/root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/libgcc2.h:203:20:
internal compiler error: Segmentation fault
 #define __NDW(a,b) __ ## a ## ti ## b
                    ^~
/root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/libgcc2.h:273:18:
note: in expansion of macro ‘__NDW’
 #define __muldi3 __NDW(mul,3)
                  ^~~~~
/root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/libgcc2.c:548:1:
note: in expansion of macro ‘__muldi3’
 __muldi3 (DWtype u, DWtype v)
 ^~~~~~~~
0x10f7d943 crash_signal
        /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/gcc/toplev.c:325
0x11f9b43c trim_filename(char const*)
        /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/gcc/diagnostic.c:1023
0x11f9d31b fancy_abort(char const*, int, char const*)
        /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/gcc/diagnostic.c:1508
0x115085d7 inchash::add_expr(tree_node const*, inchash::hash&, unsigned int)
        /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/gcc/tree.c:7426
0x10fd23a3 iterative_hash_expr
        /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/gcc/tree.h:4944
0x10fd94b3 tree_operand_hash::hash(tree_node* const&)
        /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/gcc/tree-hash-traits.h:34
0x11d677af hash
        /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/gcc/hash-map-traits.h:49
0x11d6836f get
        /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/gcc/hash-map.h:161
0x11d79437 process_store
        /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/gcc/gimple-ssa-store-merging.c:4347
0x11d79b23 execute
        /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/gcc/gimple-ssa-store-merging.c:4455


Configure (building out of tree):
configure --prefix=/opt/act-gcc-8.3.0 --enable-languages=c,c++
--disable-multilib

System:
SLES 11 SP4
Linux atmlpar32 3.0.101-63-ppc64 #1 SMP Tue Jun 23 16:02:31 UTC 2015
(4b89d0c) ppc64 ppc64 ppc64 GNU/Linux

I've tried this using the system's binutils and also binutils 2.32
with the same results (binutils 2.32 built OK).

I was previously hitting oomkiller because this host only has 500MB of
RAM.  It's been increased to 1500MB and I no longer see oomkiller in
syslog, so I don't think that's the issue any longer.

Any ideas here, or should I file a bug?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Internal Compiler Error (ICE) building gcc 8.3.0 on ppc64 Linux
  2019-03-26  1:58 Internal Compiler Error (ICE) building gcc 8.3.0 on ppc64 Linux Brian Groose
@ 2019-03-26  6:13 ` Segher Boessenkool
  2019-03-27 20:56   ` Brian Groose
  2019-03-28  3:19 ` Peter Bergner
  1 sibling, 1 reply; 5+ messages in thread
From: Segher Boessenkool @ 2019-03-26  6:13 UTC (permalink / raw)
  To: Brian Groose; +Cc: gcc-help

On Mon, Mar 25, 2019 at 06:05:43PM -0400, Brian Groose wrote:
> I was previously hitting oomkiller because this host only has 500MB of
> RAM.  It's been increased to 1500MB and I no longer see oomkiller in
> syslog, so I don't think that's the issue any longer.

Do you have a decent amount of swap installed, too?

Does the error always happen at the same spot?  Also if you use some
different make -jN option?

> Any ideas here, or should I file a bug?

Please file a PR.


Segher

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Internal Compiler Error (ICE) building gcc 8.3.0 on ppc64 Linux
  2019-03-26  6:13 ` Segher Boessenkool
@ 2019-03-27 20:56   ` Brian Groose
  0 siblings, 0 replies; 5+ messages in thread
From: Brian Groose @ 2019-03-27 20:56 UTC (permalink / raw)
  To: Segher Boessenkool; +Cc: gcc-help

On Mon, Mar 25, 2019 at 9:58 PM Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
> On Mon, Mar 25, 2019 at 06:05:43PM -0400, Brian Groose wrote:
> > I was previously hitting oomkiller because this host only has 500MB of
> > RAM.  It's been increased to 1500MB and I no longer see oomkiller in
> > syslog, so I don't think that's the issue any longer.
>
> Do you have a decent amount of swap installed, too?

I changed things to have 4GB of RAM and 4GB of swap and I still see
the same issue.

>
> Does the error always happen at the same spot?  Also if you use some
> different make -jN option?

The error always happens, even without any -j or -j1.  I also tested
other versions and 6.5.0 worked while 7.1.0 and 7.4.0 fail with the
same error.

>
> > Any ideas here, or should I file a bug?
>
> Please file a PR.

I will do that, thanks.

>
>
> Segher

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Internal Compiler Error (ICE) building gcc 8.3.0 on ppc64 Linux
  2019-03-26  1:58 Internal Compiler Error (ICE) building gcc 8.3.0 on ppc64 Linux Brian Groose
  2019-03-26  6:13 ` Segher Boessenkool
@ 2019-03-28  3:19 ` Peter Bergner
  2019-03-29 20:16   ` Brian Groose
  1 sibling, 1 reply; 5+ messages in thread
From: Peter Bergner @ 2019-03-28  3:19 UTC (permalink / raw)
  To: Brian Groose, gcc-help

On 3/25/19 5:05 PM, Brian Groose wrote:
> I am trying to build gcc 8.3.0 on linux ppc64.  I have successfully
> built 5.3.0 without issue on this machine.  When I build 8.3.0,
> however, I hit this error:
[snip]
> In file included from
> /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/libgcc2.c:56:
> /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/libgcc2.c: In
> function ‘__multi3’:
> /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/libgcc2.h:203:20:
> internal compiler error: Segmentation fault
>  #define __NDW(a,b) __ ## a ## ti ## b

This seems familiar and I think it had to do with a broken installed
header file.  Since GCC 6 and GCC 7 built successfully, can you use
one of those compilers to build GCC 8?  If so, that would lead me
to think the system compiler has issues.

Peter


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Internal Compiler Error (ICE) building gcc 8.3.0 on ppc64 Linux
  2019-03-28  3:19 ` Peter Bergner
@ 2019-03-29 20:16   ` Brian Groose
  0 siblings, 0 replies; 5+ messages in thread
From: Brian Groose @ 2019-03-29 20:16 UTC (permalink / raw)
  To: Peter Bergner; +Cc: gcc-help

On Wed, Mar 27, 2019 at 7:51 PM Peter Bergner <bergner@linux.ibm.com> wrote:
>
> On 3/25/19 5:05 PM, Brian Groose wrote:
> > I am trying to build gcc 8.3.0 on linux ppc64.  I have successfully
> > built 5.3.0 without issue on this machine.  When I build 8.3.0,
> > however, I hit this error:
> [snip]
> > In file included from
> > /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/libgcc2.c:56:
> > /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/libgcc2.c: In
> > function ‘__multi3’:
> > /root/gcc/act-gcc-8.3.0-sandbox/gcc-8.3.0/libgcc/libgcc2.h:203:20:
> > internal compiler error: Segmentation fault
> >  #define __NDW(a,b) __ ## a ## ti ## b
>
> This seems familiar and I think it had to do with a broken installed
> header file.  Since GCC 6 and GCC 7 built successfully, can you use
> one of those compilers to build GCC 8?  If so, that would lead me
> to think the system compiler has issues.

Yes, I saw similar PRs around Solaris long ago and some Sun patch
breaking things because it updated libm or something.

gcc 6.5.0 builds successfully, and when I used that to build 8.3.0, it worked!

Thank you for the suggestion!  It seems like an issue with my freshly
installed host, so I will leave it at that.  I appreciate the quick
responses, Peter and Segher!

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2019-03-29 16:37 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-03-26  1:58 Internal Compiler Error (ICE) building gcc 8.3.0 on ppc64 Linux Brian Groose
2019-03-26  6:13 ` Segher Boessenkool
2019-03-27 20:56   ` Brian Groose
2019-03-28  3:19 ` Peter Bergner
2019-03-29 20:16   ` Brian Groose

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