Re: exception propagation support not enabled in libstdc++ 4.4 on {armeabi,hppa,sparc}-linux

[Paolo Carlini <paolo dot carlini at oracle dot com>]

Hi,
>> I'm not sure if we already discussed a bit the following: would it make
>> sense to change those tests along the lines of GCC_TRY_COMPILE_OR_LINK?
>> I mean, if gcc_no_link  is yes, then we just do what we currently do, 
>> we look at the .s output, otherwise we do a test, completely analogous
>> to the one used already in libgomp, for example. That would be not just
>> for linux, but for all targets.
>>     
> Subject to fixing the bug I think is present with static-only libgcc 
> functions and C++ shared libraries (so that being able to link an 
> executable with the functions means it is also possible to link libstdc++ 
> and have the symbols resolved in that link), it would make sense to test 
> linking if possible, failing that the .s file.
>   
Ok, thanks. Then, I think I'll implement this, for now. Seems in any
case conservative to have a link type test identical to the one used in
libgomp and libgfortran and a fall back to the .s file (as currently used).

Paolo.