[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2017-02-21 Thread vsz.bugzilla at emailuser dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 vsz.bugzilla at emailuser dot net changed: What|Removed |Added Status|RESOLVED|ASSIGNED

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2017-02-21 Thread vsz.bugzilla at emailuser dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 vsz.bugzilla at emailuser dot net changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2017-02-21 Thread vsz.bugzilla at emailuser dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #13 from vsz.bugzilla at emailuser dot net --- Repeating the minimal tests with MSYS2 `mingw-w64-{i686,x86_64}-binutils-2.27-4-any` (the build that includes the proposed patch), it seems the problem is now fixed for both 32-bit and 64

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-13 Thread vsz.bugzilla at emailuser dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #11 from vsz.bugzilla at emailuser dot net --- Thank you, Nick. I'd be glad to make tests with a binary pre-built using your patches, but building binutils from source myself, appears to be a too long shot at this point. Is

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-12 Thread vsz.bugzilla at emailuser dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #8 from vsz.bugzilla at emailuser dot net --- And the link command output: ``` Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=C:/msys64/mingw32/bin/../lib/gcc/i686-w64-mingw32/5.4.0/lto-wrapper.exe Target: i686-w64-mingw32

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-12 Thread vsz.bugzilla at emailuser dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #7 from vsz.bugzilla at emailuser dot net --- Created attachment 38883 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38883&action=edit Test case #1 Attached a test case that includes all referred sources, generated .o b

[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

2016-07-11 Thread vsz.bugzilla at emailuser dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880 --- Comment #5 from vsz.bugzilla at emailuser dot net --- You may find a self-contained example under the GitHub link included in the original report. Direct link: https://github.com/Alexpux/MSYS2-packages/issues/454#issuecomment-186433276

[Bug c/69880] New: Linking Windows resources + implicit 'default-manifest.o' creates bad .exe

2016-02-19 Thread vsz.bugzilla at emailuser dot net
Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: vsz.bugzilla at emailuser dot net Target Milestone: --- Hi, Sorry for the ambiguous title, I'm not completely sure where/what is the culprit yet. Please bear