--- Comment #5 from alessandro dot mei at elsagdatamat dot com 2007-06-12
15:41 ---
(In reply to comment #4)
> And why do you think GCC is at fault? It is hard to debug this huge sources
> really. Have you tried to pin point exactly where the issue. Do you have any
> unin
--- Comment #3 from alessandro dot mei at elsagdatamat dot com 2007-06-12
13:48 ---
the exact version of GCC;
the system type;
the options given when GCC was configured/built;
gcc -v
Using built-in specs.
Target: powerpc-ibm-aix5.3.0.0
Configured with: ../gcc
--- Comment #2 from alessandro dot mei at elsagdatamat dot com 2007-06-12
13:42 ---
(From update of attachment 13685)
the complete command line that triggers the bug:
/home/mag/sviluppo/bin/bkeuti /home/mag/sviluppo/config/bkeuti.xml
/home/mag/sviluppo/config/processi.dtd > /dev/n
--- Comment #1 from alessandro dot mei at elsagdatamat dot com 2007-06-12
13:30 ---
Created an attachment (id=13685)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13685&action=view)
compiler output and warnings; the preprocessed file (*.ii) that triggers the
bug
the c
Version: 4.1.1
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: alessandro dot mei at elsagdatamat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32288
