Adriaan van Os wrote:
Waldek Hebisch wrote:
I have now "almost ready" experimental gcc-4.1.0 port. There are some minor problems but
basically 4.1.0 port should be now as good (or as bad...) as 4.0.3 port. I would > like to fix some extra problems (most of them not related to port) and add some feature before I make a new snapshot, so ATM I have made port available as patches:
Thanks for the new diffs for gcc-4.1.0 !
I tried them, but the build dies with:
../.././xgpc -B../.././ -c -I. -W -Wall -Wmissing-prototypes -Wmissing-declarations -g -DHAVE_DESIGNATED_INITIALIZERS=0 -DENABLE_CHECKING -DENABLE_ASSERT_CHECKING --unit-path=/Users/adriaan/gpc/gpc-20060325/gcc-41/gcc-4.1.0/gcc/p/rts --automake -DRTS_RELEASE_STRING="'`cat /Users/adriaan/gpc/gpc-20060325/gcc-41/gcc-4.1.0/gcc/p/rts/rts-version`'" -DGCC_VERSION="''" "/Users/adriaan/gpc/gpc-20060325/gcc-41/gcc-4.1.0/gcc/p/rts/files.pas" /Users/adriaan/gpc/gpc-20060325/gcc-41/gcc-4.1.0/gcc/p/rts/files.pas: In function `CanRead': /Users/adriaan/gpc/gpc-20060325/gcc-41/gcc-4.1.0/gcc/p/rts/files.pas:1878: error: invalid initializer for set
I can not reproduce the problem. Since the compiler semm to be build one can try to copy RTS (libgpc.a) compiled using different backend into build directory and run the testsuite to get more information.
Also, could you try the following patch (it should print internal information about failing set initializers):
--- gcc-4.1.0/gcc/tree.c.pp 2006-04-11 02:18:02.158210824 +0200 +++ gcc-4.1.0/gcc/tree.c 2006-04-11 02:18:24.782771368 +0200 @@ -6013,6 +6013,7 @@
if (lo_index < low_limit || hi_index >= bit_size) { + debug_tree (vals); error ("invalid initializer for set"); return NULL_TREE; } @@ -6031,6 +6032,7 @@ = tree_low_cst (TREE_VALUE (vals), 0) - domain_min; if (index < 0 || index >= bit_size) { + debug_tree (vals); error ("invalid initializer for set"); return NULL_TREE; }