This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [testsuite] don't use lto plugin if it doesn't work
- From: Mike Stump <mikestump at comcast dot net>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: "H.J. Lu" <hjl dot tools at gmail dot com>, gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Wed, 27 Jun 2012 12:15:22 -0700
- Subject: Re: [testsuite] don't use lto plugin if it doesn't work
- References: <orfw9hbx8p.fsf@livre.localdomain> <AED76334-441D-4270-875A-0B65CEB403BF@comcast.net> <CAMe9rOpdfb=JXDvLdDVxKm3+GoAY8Nr3OHg2rbtgsYBjH2Z0uw@mail.gmail.com> <orfw9h9l8a.fsf@livre.localdomain>
On Jun 27, 2012, at 2:07 AM, Alexandre Oliva wrote:
> Why? We don't demand a working plugin. Indeed, we disable the use of
> the plugin if we find a linker that doesn't support it. We just don't
> account for the possibility of finding a linker that supports plugins,
> but that doesn't support the one we'll build later.
If this is the preferred solution, then having configure check the 64-bitness of ld and turning off the plugin altogether on mismatches sounds like a reasonable course of action to me.