Re: [PATCH] Make LTO tests that require recent binutils UNSUPPORTED with older ones (PR lto/86004)

2018-12-11 Thread Rainer Orth
Hi Jakub, > On Tue, Dec 11, 2018 at 08:52:12AM +0100, Rainer Orth wrote: >> Hi Jakub, >> >> > As mentioned in the PR, older binutils (like 2.25) complain on these tests >> > when using -r that: >> > plugin needed to handle lto object >> > The following patch introduces an effective target and gua

Re: [PATCH] Make LTO tests that require recent binutils UNSUPPORTED with older ones (PR lto/86004)

2018-12-11 Thread Jakub Jelinek
On Tue, Dec 11, 2018 at 08:52:12AM +0100, Rainer Orth wrote: > Hi Jakub, > > > As mentioned in the PR, older binutils (like 2.25) complain on these tests > > when using -r that: > > plugin needed to handle lto object > > The following patch introduces an effective target and guards those tests on

Re: [PATCH] Make LTO tests that require recent binutils UNSUPPORTED with older ones (PR lto/86004)

2018-12-11 Thread Richard Biener
On Tue, 11 Dec 2018, Jakub Jelinek wrote: > Hi! > > As mentioned in the PR, older binutils (like 2.25) complain on these tests > when using -r that: > plugin needed to handle lto object > The following patch introduces an effective target and guards those tests on > a linker with this issue fixed

Re: [PATCH] Make LTO tests that require recent binutils UNSUPPORTED with older ones (PR lto/86004)

2018-12-10 Thread Rainer Orth
Hi Jakub, > As mentioned in the PR, older binutils (like 2.25) complain on these tests > when using -r that: > plugin needed to handle lto object > The following patch introduces an effective target and guards those tests on > a linker with this issue fixed. > > Regtested on x86_64-linux and i686-

[PATCH] Make LTO tests that require recent binutils UNSUPPORTED with older ones (PR lto/86004)

2018-12-10 Thread Jakub Jelinek
Hi! As mentioned in the PR, older binutils (like 2.25) complain on these tests when using -r that: plugin needed to handle lto object The following patch introduces an effective target and guards those tests on a linker with this issue fixed. Regtested on x86_64-linux and i686-linux, plus regtest