On Sat, 2 May 2009, Paolo Carlini wrote: > 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. -- Joseph S. Myers jos...@codesourcery.com
