On Fri, 18 Sep 2009, Jack Howarth wrote:
> Richard,
>We have an analysis on the cause of the breakage of
> exception handling at r147995 on x86_64-apple-darwin10 (PR41260)...
>
> http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-September/025908.html
> http://lists.cs.uiuc.edu/pipermail/llvmdev
Joseph S. Myers wrote:
> On Fri, 18 Sep 2009, Jack Howarth wrote:
>
>>I can confirm that the second proposed solution of passing
>> -Wl,-no_compact_unwind
>> to the linkage of the g++.dg/torture/stackalign/eh-vararg-2.C test cases
>> eliminates
>> the execution error on x86_64-apple-darwin10
On Fri, 18 Sep 2009, Jack Howarth wrote:
>I can confirm that the second proposed solution of passing
> -Wl,-no_compact_unwind
> to the linkage of the g++.dg/torture/stackalign/eh-vararg-2.C test cases
> eliminates
> the execution error on x86_64-apple-darwin10 so that option works. This lead
I can confirm that the second proposed solution of passing
-Wl,-no_compact_unwind
to the linkage of the g++.dg/torture/stackalign/eh-vararg-2.C test cases
eliminates
the execution error on x86_64-apple-darwin10 so that option works. This leads
to a
dejagnu question. I want to do a quick and d
FYI, to clarify for others who haven't been following
PR41260, the messages...
http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-September/025894.html
http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-September/025898.html
explain the changes in libgcc handling as of darwin10. If I
understand thos
Richard,
We have an analysis on the cause of the breakage of
exception handling at r147995 on x86_64-apple-darwin10 (PR41260)...
http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-September/025908.html
http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-September/025909.html
The additional epilog unw
