On Mon, Jul 1, 2019 at 5:27 PM Vincent Lefevre wrote:
>
> On 2019-07-01 16:59:06 +0200, Marc Glisse wrote:
> > On Mon, 1 Jul 2019, Vincent Lefevre wrote:
> > > I suggest another solution:
> > >
> > > First try like now. If the format is unknown, check whether the
> > > object file contains the
Vincent Lefevre writes:
Yes, with LTO, the object file does not contain the structure as is.
Thus the detection from "od -b conftest.$OBJEXT" does not work.
That could be solved by generating a final executable, right?
--
Torbjörn
Please encrypt, key id 0xC8601622
On 2019-07-01 16:59:06 +0200, Marc Glisse wrote:
> On Mon, 1 Jul 2019, Vincent Lefevre wrote:
> > I suggest another solution:
> >
> > First try like now. If the format is unknown, check whether the
> > object file contains the string ".gnu.lto" (which should mean
> > that GCC was used with LTO),
On 2019-07-01 16:36:23 +0200, Torbjorn Granlund wrote:
> Vincent Lefevre writes:
>
> I suggest another solution:
>
> First try like now. If the format is unknown, check whether the
> object file contains the string ".gnu.lto" (which should mean
> that GCC was used with LTO), and in this
On Mon, 1 Jul 2019, Vincent Lefevre wrote:
On 2019-07-01 13:44:04 +0200, Marc Glisse wrote:
On Mon, 1 Jul 2019, Martin Liška wrote:
> On 6/24/19 8:57 PM, Marc Glisse wrote:
> > On Mon, 24 Jun 2019, Martin Liška wrote:
> >
> > > Using -flto one can see a test failure:
> >
> > This is well
Vincent Lefevre writes:
I suggest another solution:
First try like now. If the format is unknown, check whether the
object file contains the string ".gnu.lto" (which should mean
that GCC was used with LTO), and in this case, try again with
"-fno-lto" as the patch was doing.
That
On 2019-07-01 13:44:04 +0200, Marc Glisse wrote:
> On Mon, 1 Jul 2019, Martin Liška wrote:
>
> > On 6/24/19 8:57 PM, Marc Glisse wrote:
> > > On Mon, 24 Jun 2019, Martin Liška wrote:
> > >
> > > > Using -flto one can see a test failure:
> > >
> > > This is well known, see the archives for
On Mon, 1 Jul 2019, Martin Liška wrote:
On 6/24/19 8:57 PM, Marc Glisse wrote:
On Mon, 24 Jun 2019, Martin Liška wrote:
Using -flto one can see a test failure:
This is well known, see the archives for details. It is a combination of 2
issues:
- (thin) LTO prevents configure from guessing
On 6/24/19 8:57 PM, Marc Glisse wrote:
> On Mon, 24 Jun 2019, Martin Liška wrote:
>
>> Using -flto one can see a test failure:
>
> This is well known, see the archives for details. It is a combination of 2
> issues:
> - (thin) LTO prevents configure from guessing the floating point format
> - a
