[Bug c++/19630] Program hangs when compiling the testcase with -m64 option.
--- Additional Comments From shebs at apple dot com 2005-01-25 22:47 --- Subject: Re: Program hangs when compiling the testcase with -m64 option. pinskia at gcc dot gnu dot org wrote: >--- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-25 >21:15 --- >(In reply to comment #0) > > >>The GCC compiler that I am using has the following information: >> >> >Can you report this to Apple since that is looks like either a dyld problem or >a linker problem because >the assembly produced by -m32 and -m64 were about the same in that the only >changes were needed >for 64bit? > >Also there is no way outside of Apple right now to reproduce this unless you >have a tiger machine on a >G5. > >Stan could you look into this? > > > OK. Stan -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19630
[Bug c++/19630] Program hangs when compiling the testcase with -m64 option.
--- Additional Comments From shebs at apple dot com 2005-01-25 23:10 --- (In reply to comment #0) > The GCC compiler that I am using has the following information: > Reading specs from /usr/lib/gcc/powerpc-apple-darwin8/4.0.0/specs > Configured with: /private/var/tmp/gcc/gcc-4031.obj~3/src/configure --disable- > checking --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj- > c++ --program-transform-name=/^[cg][^+.-]*$/s/$/-4.0/ --with-gxx-include- > dir=/include/gcc/darwin/4.0/c++ --build=powerpc-apple-darwin8 --host=powerpc- > apple-darwin8 --target=powerpc-apple-darwin8 > Thread model: posix > gcc version 4.0.0 20041026 (Apple Computer, Inc. build 4031) > > Compiled the testcase with -m64 option, the program hangs forever. Without > the - > m64 option, the problem goes away and gives the correct return code: 10. Seems to work in latest Tiger. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19630
[Bug middle-end/18574] [4.0 Regression] bootstrap comprison failed
--- Additional Comments From shebs at apple dot com 2004-11-22 00:24 --- Subject: Re: [4.0 Regression] bootstrap comprison failed Jeffrey A Law wrote: >I've been unable to reproduce the comparison failures. However, as I >outlined in an earlier message, I have come up with a scenario in which >my patch might cause a comparison failure. > > This fixes bootstrap compare failures on Darwin, thank you saving me from the horrible debugging hell I was dreading when I saw miscompares last night... :-) Stan >This patch changes the hashing routine to use block indices rather >than hash on pointers. That ought to stabilize the hash (and thus the >hash table traversals and SSA_NAME coalescing) in cases where it >was unstable before. > >Since I've been unable to trigger the failure here, I can't say for >certain whether or not this patch fixes the bootstrap failures others >have seen. > >FWIW, this has been bootstrapped and regression tested on >i686-pc-linux-gnu. > > > > > > > * tree-ssa-threadupdate.c (redirection_data_hash): Use the > index of the destination block for the hash value rather than > hashing a pointer. > >Index: tree-ssa-threadupdate.c >=== >RCS file: /cvs/gcc/gcc/gcc/tree-ssa-threadupdate.c,v >retrieving revision 2.15 >diff -c -p -r2.15 tree-ssa-threadupdate.c >*** tree-ssa-threadupdate.c20 Nov 2004 12:48:13 - 2.15 >--- tree-ssa-threadupdate.c21 Nov 2004 15:00:33 - >*** static hashval_t >*** 203,209 > redirection_data_hash (const void *p) > { >edge e = ((struct redirection_data *)p)->outgoing_edge; >! return htab_hash_pointer (e); > } > > static int >--- 203,209 > redirection_data_hash (const void *p) > { >edge e = ((struct redirection_data *)p)->outgoing_edge; >! return e->dest->index; > } > > static int > -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18574