[Bug ld/16790] [cygwin|mingw] ld -v creates a.exe

https://sourceware.org/bugzilla/show_bug.cgi?id=16790 Corinna Vinschen changed: What|Removed |Added CC||ktietz at redhat dot com --- Comme

[Bug ld/16790] [cygwin|mingw] ld -v creates a.exe

https://sourceware.org/bugzilla/show_bug.cgi?id=16790 --- Comment #5 from Corinna Vinschen --- > GCC could handle the fact to add a default manifest only when building > executables If that's not clear: I'm referring to the fact that, right now, with the default-manifest.o file being referred b

[Bug ld/16790] [cygwin|mingw] ld -v creates a.exe

https://sourceware.org/bugzilla/show_bug.cgi?id=16790 --- Comment #6 from Corinna Vinschen --- After some discussion with Jon_Y and Yaakov on IRC, I'm pretty much ok with moving the default-manifest handling to GCC. I'm just wondering if the default-manifest shouldn't then be made into its own p

[Bug ld/16790] [cygwin|mingw] ld -v creates a.exe

https://sourceware.org/bugzilla/show_bug.cgi?id=16790 --- Comment #8 from Corinna Vinschen --- (In reply to Nick Clifton from comment #7) Hi Nick, > Hi Corinna, > > > After some discussion with Jon_Y and Yaakov on IRC, I'm pretty much ok > > with moving the default-manifest handling to GCC. >

[Bug ld/16790] [cygwin|mingw] ld -v creates a.exe

https://sourceware.org/bugzilla/show_bug.cgi?id=16790 --- Comment #9 from Corinna Vinschen --- (In reply to Corinna Vinschen from comment #8) > (In reply to Nick Clifton from comment #7) > > > I'm just wondering if the default-manifest shouldn't then be made > > > into its own package, independen

[Bug ld/16821] New: x86_64 PE/COFF: ld truncates addresses of symbols from linker scripts to 32 bit

Severity: critical Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: corinna at vinschen dot de I just encountered a serious bug while building the Cygwin DLL for x86_64-pc-cygwin, which I never noticed before (*blush*): The Cygwin

[Bug ld/16821] x86_64 PE/COFF: ld truncates addresses of symbols from linker scripts to 32 bit

https://sourceware.org/bugzilla/show_bug.cgi?id=16821 --- Comment #3 from Corinna Vinschen --- Hi Nick, thanks for the patch. (In reply to Nick Clifton from comment #2) > I have uploaded a patch which is a partial fix for the problem. It > detects out-of-range absolute values and tries to co

[Bug ld/16821] x86_64 PE/COFF: ld truncates addresses of symbols from linker scripts to 32 bit

https://sourceware.org/bugzilla/show_bug.cgi?id=16821 Corinna Vinschen changed: What|Removed |Added CC||ktietz at redhat dot com --- Comme

[Bug ld/16835] New: PE/COFF: __image_base__ and __ImageBase have different values

Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: corinna at vinschen dot de Created attachment 7549 --> https://sourceware.org/bugzilla/attachment.cgi?id=7549&action=edit Fix __ImageBase value for DLLs rebased to a fixed v

[Bug ld/16835] PE/COFF: __image_base__ and __ImageBase have different values

https://sourceware.org/bugzilla/show_bug.cgi?id=16835 --- Comment #1 from Corinna Vinschen --- Hang on. My patch changes the value of __ImageBase inside of ld, but in the resulting DLL it's still the old default value. I don't see why this happens :( Sorry, Corinna -- You are receiving this

[Bug binutils/18025] New: dwarf2 debug info after rebasing DLLs unusable

Component: binutils Assignee: unassigned at sourceware dot org Reporter: corinna at vinschen dot de Target: cygwin, i686 and x86_64 Hi, we're encountering a problem evaluating Dwarf2 debug info in DLLs after rebasing the DLL. Rebasing, that is, moving the image

[Bug binutils/18025] dwarf2 debug info after rebasing DLLs unusable

https://sourceware.org/bugzilla/show_bug.cgi?id=18025 --- Comment #9 from Corinna Vinschen --- Hi Nick, thanks a lot for the patch. I'll look into getting a new binutils for the Cygwin distro soon. Thanks, Corinna -- You are receiving this mail because: You are on the CC list for the bug.