[Bug target/20673] [4.0 only] C PCH testsuite assembly comparison failure

2005-04-15 Thread davem at gcc dot gnu dot org
--- Additional Comments From davem at gcc dot gnu dot org 2005-04-15 19:26 --- This should be fixed both in mainline and the 4.0 branch -- What|Removed |Added

[Bug target/43004] New: sparc 64-bit stack slot allocation overlaps with alloca

2010-02-08 Thread davem at gcc dot gnu dot org
iority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: davem at gcc dot gnu dot org GCC build triplet: sparc-unknown-linux-gnu GCC host triplet: sparc-unknown-linux-gnu GCC target triplet: sparc-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43004

[Bug target/43004] sparc 64-bit stack slot allocation overlaps with alloca

2010-02-09 Thread davem at gcc dot gnu dot org
--- Comment #1 from davem at gcc dot gnu dot org 2010-02-09 22:08 --- Ok, I now know a lot more about this bug. It's effects were masked before gcc-4.4 because we used to have the TFmode secondary reload slot in every stack frame. That got removed by my commit: 2009-01-04 Da

[Bug target/43004] sparc 64-bit stack slot allocation overlaps with alloca

2010-02-09 Thread davem at gcc dot gnu dot org
--- Comment #2 from davem at gcc dot gnu dot org 2010-02-09 22:13 --- Reading further, the Sparc 64-bit ABI requires that the every stack frame be 16 byte aligned. And if that were the case this problem would never happen. Will try to determine how the stack is becomming only 8-byte

[Bug target/43004] sparc 64-bit stack slot allocation overlaps with alloca

2010-02-09 Thread davem at gcc dot gnu dot org
--- Comment #3 from davem at gcc dot gnu dot org 2010-02-10 00:49 --- I've root caused this to the Linux kernel not 16-byte aligning thread stacks when using the clone() system call (it was enforcing only 8-byte alignment), and also signal stacks. The seconday mem TFmode stack slo

[Bug middle-end/34668] [4.3 Regression] ICE in find_compatible_field with -combine

2010-03-12 Thread davem at gcc dot gnu dot org
--- Comment #13 from davem at gcc dot gnu dot org 2010-03-12 20:58 --- I'm still seeing this fail on 32-bit sparc with mainline: home/davem/src/GIT/GCC/gcc/gcc/testsuite/gcc.dg/pr34668-2.c: In function 'set_conv_libfunc': /home/davem/src/GIT/GCC/gcc/gcc/testsuite/gcc.d

[Bug tree-optimization/38819] [4.3 Regression] trapping expression wrongly hoisted out of loop

2010-03-12 Thread davem at gcc dot gnu dot org
--- Comment #19 from davem at gcc dot gnu dot org 2010-03-12 21:00 --- Like Eric I'm still seeing this fail on mainline on 32-bit sparc. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38819

[Bug c/43385] New: glibc regex testsuite failures

2010-03-15 Thread davem at gcc dot gnu dot org
glibc regex testsuite failures Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: davem at gcc dot gnu dot org GCC build tr

[Bug c/43385] [4.5 Regression] glibc regex testsuite failures

2010-03-23 Thread davem at gcc dot gnu dot org
--- Comment #3 from davem at gcc dot gnu dot org 2010-03-23 20:40 --- Sorry, it's taking a long time to sort out the test case. The GLIBC regex code is huge and non-trivial. However I did track down that it might be dependent upon optimization options, for example I can reproduce

[Bug bootstrap/21162] Build failure

2005-04-23 Thread davem at gcc dot gnu dot org
--- Additional Comments From davem at gcc dot gnu dot org 2005-04-22 18:08 --- Yes, it should just "work". And it would have if you: 1) Make sure /lib64/libc.so.6 is installed. 2) Delete the file /etc/disable_64_gcc Then gcc would output 64-bit code by default when

[Bug bootstrap/21162] Build failure

2005-04-23 Thread davem at gcc dot gnu dot org
--- Additional Comments From davem at gcc dot gnu dot org 2005-04-22 18:21 --- Right, it can't compile a test program with "-m64" because the /lib64/libc.so.6 package is not installed. Also, when you use "sparc32" you should use it to create a complete e

[Bug bootstrap/21162] Build failure

2005-04-23 Thread davem at gcc dot gnu dot org
--- Additional Comments From davem at gcc dot gnu dot org 2005-04-22 18:27 --- You may with to restart your build with the correct environment setup, just to be safe. Depending upon what you've enabled it can take a long time :-) Yes, the /etc/disable_64_gcc file is what prevent