This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

remaining new darwin regressions


  Currently i686-apple-darwin9 appears in very good shape for
gcc 4.4 with the exception of one new set of testsuite failures
related to the new stackalignment changes. These all share the
commmon feature of only failing with the -O3 -g compiler option
flags...

FAIL: g++.dg/torture/stackalign/eh-alloca-1.C  -O3 -g  execution test
FAIL: g++.dg/torture/stackalign/eh-vararg-1.C  -O3 -g  execution test
FAIL: g++.dg/torture/stackalign/eh-vararg-2.C  -O3 -g  execution test
FAIL: g++.dg/torture/stackalign/throw-1.C  -O3 -g  execution test
FAIL: g++.dg/torture/stackalign/eh-alloca-1.C  -O3 -g  execution test
FAIL: g++.dg/torture/stackalign/eh-vararg-1.C  -O3 -g  execution test
FAIL: g++.dg/torture/stackalign/eh-vararg-2.C  -O3 -g  execution test
FAIL: g++.dg/torture/stackalign/throw-1.C  -O3 -g  execution test

With -O3 alone, these test cases don't fail there execution tests.
Mike Stump looked at the assembly code from eh-alloca-1.C and said
he doesn't believe this is a bug in the Darwin assembler or linker
but rather in gcc itself. Does anyone familiar with stackalign
changes have access to Intel Darwin9 to take a look at this? These
failures are currently the last bit of PR37012. Thanks in advance
for any efforts to eliminate these.
              Jack


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]