This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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]

Re: [RFC] Do we care about binary compatibility of code produced by cross-compilers?


Paolo Carlini wrote:
Even more interesting, I would say mysterious, libjava' configure.ac, like libsdc++-v3', has GCC_NO_EXECUTABLES on top. Do you understand better than me, what's going on here?
I think the "solution" of the mystery is that GCC_NO_EXECUTABLES boils down to testing the linker and setting gcc_no_link appropriately. Thus, when cross-compiling, it can well be that the linker works (as I understand it), thus link tests are allowed. Good.

Now, if, for some reason, GCC_NO_EXECUTABLES sets gcc_no_link = yes, configuring a cross-compiler library which has GCC_NO_EXECUTABLES on top and GCC_CHECK_TLS somewhere after it fails completely, with "Link tests are not allowed after GCC_NO_EXECUTABLES"

As I see that issue, libstdc++-v3' configure.ac, at variance with libjava', doesn't have this problem. I'm not at all sure we want it for libstdc++-v3, on the basis that it would allow in exchange to run GCC_CHECK_TLS and GCC_CHECK_UNWIND_GETIPINFO unconditionally, without changing anything else.

Opinions?

Paolo.


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