public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tammer at tammer dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/38606] AIX: build failed in stage 2
Date: Mon, 22 Dec 2008 15:17:00 -0000	[thread overview]
Message-ID: <20081222151638.3569.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38606-15635@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from tammer at tammer dot net  2008-12-22 15:16 -------
Hello,
some additions:

The same happens for genautomata.c.

/opt/freeware/src/packages/BUILD/gcc-build/./prev-gcc/xgcc
-B/opt/freeware/src/packages/BUILD/gcc-build/./prev-gcc/
-B/opt/freeware/powerpc-ibm-aix5.3.0.0/bin/ -c   -g -O2 -DIN_GCC   -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros       
                             -Wno-overlength-strings    -DHAVE_CONFIG_H
-DGENERATOR_FILE -I. -Ibuild -I../../gcc-4.3.2/gcc -I../../gcc-4.3.2/gcc/build
-I../../gcc-4.3.2/gcc/../include -I../../gcc-4.3.2/gcc/../libcpp/include 
-I../../gcc-4.3.2/gcc/../libdecnumber -I../../gcc-4.3.2/gcc/../libdecnumber/dpd
-I../libdecnumber -I/opt/freeware/include   -o build/genautomata.o
../../gcc-4.3.2/gcc/genautomata.c
: In function 'create_automata':
:6534: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
gmake[3]: *** [build/genautomata.o] Error 1


I have successfully tried to produce the preprocessed output with -E. This
worked OK. 

After that I could compile the two preprocessed files with 4.2.4 gcc -c xxx.c
... With 4.3.2 gcc the same error happens:

export PATH=/opt/freeware/src/packages/BUILD/gcc-build/prev-gcc:$PATH;xgcc  -c
insn-attrtab.prep.c
../../gcc-4.3.2/gcc/config/rs6000/rs6000.md: In function
'internal_dfa_insn_code':
../../gcc-4.3.2/gcc/config/rs6000/rs6000.md:148: internal compiler error:
Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

I will upload the two files.

Bye
  Rainer

P.S.:
# ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        32768
memory(kbytes)       32768
coredump(blocks)     2097151
nofiles(descriptors) 2000


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38606


  parent reply	other threads:[~2008-12-22 15:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-22 14:53 [Bug c/38606] New: " tammer at tammer dot net
2008-12-22 14:54 ` [Bug c/38606] " tammer at tammer dot net
2008-12-22 14:55 ` tammer at tammer dot net
2008-12-22 14:56 ` tammer at tammer dot net
2008-12-22 14:56 ` tammer at tammer dot net
2008-12-22 15:17 ` tammer at tammer dot net [this message]
2008-12-22 15:18 ` tammer at tammer dot net
2008-12-22 15:18 ` tammer at tammer dot net
2008-12-22 16:06 ` [Bug other/38606] " pinskia at gcc dot gnu dot org
2008-12-23  7:25 ` tammer at tammer dot net
2008-12-23  8:36 ` tammer at tammer dot net
2009-01-12  7:12 ` tammer at tammer dot net
2009-02-06 13:34 ` rosenhauer at dkrz dot de
2009-02-08  9:39 ` tammer at tammer dot net
2009-06-13 13:23 ` vovata at gmail dot com
2009-06-13 14:18 ` tammer at tammer dot net
2009-06-13 20:31 ` vovata at gmail dot com
2009-07-19 16:53 ` tammer at tammer dot net

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=20081222151638.3569.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).