remaining new darwin regressions

[H.J. Lu]

On Tue, Jan 20, 2009 at 3:29 PM, Jack Howarth <howarth@bromo.med.uc.edu> wrote:
>  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.

Are those assembly codes correct? If not, what are the problems?



-- 
H.J.