bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/18199] ld fails with -flto for mingw, wrong resolution for main


From: address@hidden
Subject: [Bug ld/18199] ld fails with -flto for mingw, wrong resolution for main
Date: Mon, 30 Dec 2019 14:14:58 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=18199

Rainer Emrich <address@hidden> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from Rainer Emrich <address@hidden> ---
(In reply to Hannes Domani from comment #7)
> (In reply to address@hidden from comment #6)
> > The binutils-2_26-branch branch has been updated by Kwok Yeung
> > <address@hidden>:
> > 
> > https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;
> > h=412d26bde8585eca3ec6b8bed70197205288cbdf
> > 
> > commit 412d26bde8585eca3ec6b8bed70197205288cbdf
> > Author: Kwok Cheung Yeung <address@hidden>
> > Date:   Thu Dec 10 16:11:07 2015 +0000
> > 
> >     ld: Fix LTO for MinGW targets
> >     
> >     When creating a dummy BFD for an IR file, the output BFD is used as
> >     a template for the new BFD, when it needs to be the input BFD passed
> >     into the function when not dealing with a BFD plugin.
> >     
> >     On most targets this is not an issue as the input and output formats
> >     are the same anyway, but on MinGW targets, there are two variant
> >     formats used (pe-i386/pe-x86-64 and pei-i386/pei-x86-64) which are
> >     similar but not interchangeable here.
> >     
> >             PR ld/18199
> >             * plugin.c (plugin_get_ir_dummy_bfd): Use srctemplate as the
> >             template when calling bfd_create if it does not use the BFD
> >             plugin target vector.
> >     
> >     (Cherry-picked from commit 4a07dc81356ed8728e204e9aabeb256703c59aef)
> 
> Wasn't this bug fixed with this commit?

Yes, I think that's fixed. At least it doesn't reproduce with newer versions.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]