[Bug ld/32675] Wine binaries built with binutils 2.44 no longer run

2025-03-11 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32675 --- Comment #17 from LIU Hao --- (In reply to Jeremy Drake from comment #16) > I kind of got the impression that section names were limited to 8 > characters. If that's not true, I could use better section names like in > that merge request.

[Bug ld/32675] Wine binaries built with binutils 2.44 no longer run

2025-03-08 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32675 LIU Hao changed: What|Removed |Added Attachment #15990|0 |1 is obsolete|

[Bug ld/32675] Wine binaries built with binutils 2.44 no longer run

2025-03-07 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32675 --- Comment #14 from LIU Hao --- Created attachment 15990 --> https://sourceware.org/bugzilla/attachment.cgi?id=15990&action=edit proposed patch This is a patch that makes DLLTOOL emit delay-import data into `.didat` [1] instead of `.idata`

[Bug ld/32675] Wine binaries built with binutils 2.44 no longer run

2025-02-10 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32675 --- Comment #11 from LIU Hao --- Please see the patch attached in https://sourceforge.net/p/mingw-w64/mailman/message/59129001/ -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/32675] Wine binaries built with binutils 2.44 no longer run

2025-02-10 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32675 --- Comment #9 from LIU Hao --- Yeah the MSVC delayimp facilities have code to temporarily unprotect the import table before filling in those pointers; see 'C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.43.34808\incl

[Bug ld/32675] Wine binaries built with binutils 2.44 no longer run

2025-02-10 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32675 --- Comment #8 from LIU Hao --- After a glance at Wine RegEdit source, I feel that this is caused by delayimp. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/32675] Wine binaries built with binutils 2.44 no longer run

2025-02-10 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32675 --- Comment #7 from LIU Hao --- ``` 7FFA9AF3C81C

[Bug ld/32675] Wine binaries built with binutils 2.44 no longer run

2025-02-10 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32675 --- Comment #3 from LIU Hao --- MSYS2 has upgraded their binutils since some days ago: https://github.com/msys2/MINGW-packages/commit/830d2ccff7811106a3c4254599737c957f688b06 I haven't heard of such issues. It looks like that Wine requires .C

[Bug ld/32264] For Windows,`.CRT` section should be merged into `.rdata`

2025-02-10 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32264 --- Comment #12 from LIU Hao --- (In reply to Mike Lothian from comment #11) > Hi > > This patch has broken wine for me > > https://sourceware.org/bugzilla/show_bug.cgi?id=32675 > https://bugs.winehq.org/show_bug.cgi?id=57819 I have comment

[Bug ld/32675] Wine binaries built with binutils 2.44 no longer run

2025-02-10 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32675 LIU Hao changed: What|Removed |Added CC||lh_mouse at 126 dot com --- Comment #1

[Bug binutils/32531] [GAS] Intel Assembly Bugs (Mishandle Directive Names)

2025-01-09 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32531 LIU Hao changed: What|Removed |Added CC||lh_mouse at 126 dot com --- Comment #1

[Bug ld/32264] For Windows,`.CRT` section should be merged into `.rdata`

2024-11-27 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32264 --- Comment #10 from LIU Hao --- Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

[Bug binutils/32337] New: dlltool -m option does not change type of some .o files in an import library

2024-11-03 Thread lh_mouse at 126 dot com
Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: lh_mouse at 126 dot com Target Milestone: --- Given this file 'my.def' LIBRARY "my.dll" EXPORTS foo It seems possib

[Bug ld/32264] For Windows,`.CRT` section should be merged into `.rdata`

2024-11-03 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32264 LIU Hao changed: What|Removed |Added Attachment #15756|0 |1 is obsolete|

[Bug ld/32264] For Windows,`.CRT` section should be merged into `.rdata`

2024-11-03 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32264 --- Comment #7 from LIU Hao --- Created attachment 15776 --> https://sourceware.org/bugzilla/attachment.cgi?id=15776&action=edit final patch 2/2 The previous broke pseudo relocation because it expected pseudo relocation list ended immediate

[Bug ld/32264] For Windows,`.CRT` section should be merged into `.rdata`

2024-11-03 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32264 LIU Hao changed: What|Removed |Added Attachment #15755|0 |1 is obsolete|

[Bug ld/32264] For Windows,`.CRT` section should be merged into `.rdata`

2024-10-22 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32264 --- Comment #5 from LIU Hao --- Created attachment 15756 --> https://sourceware.org/bugzilla/attachment.cgi?id=15756&action=edit Second patch for merging .CRT, .ctors and .dtors into .data `.CRT$XD*` sections also exist in mingw-w64 CRT and

[Bug ld/31092] SECREL32 produces wrong value on x86_64-w64-mingw32

2024-10-22 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31092 LIU Hao changed: What|Removed |Added Component|gas |ld Resolution|---

[Bug ld/32264] For Windows,`.CRT` section should be merged into `.rdata`

2024-10-22 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32264 --- Comment #4 from LIU Hao --- Created attachment 15755 --> https://sourceware.org/bugzilla/attachment.cgi?id=15755&action=edit Partial patch to make `.idata` and `.CRT` read-only. Partial patch to make `.idata` and `.CRT` read-only. Wind

[Bug ld/32264] For Windows,`.CRT` section should be merged into `.rdata`

2024-10-20 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32264 --- Comment #3 from LIU Hao --- Also `__imp_` pointers are also read-only for MSVC and LLD, but not LD. I don't know in details how they are implemented; they also seem to be merged into `.rdata`. ``` $ nm --defined-only /usr/x86_64-w64-mingw

[Bug ld/32264] For Windows,`.CRT` section should be merged into `.rdata`

2024-10-11 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32264 --- Comment #2 from LIU Hao --- And there's more; actually all these sections are merged into `.rdata`: (https://github.com/llvm/llvm-project/blob/ebeb56af5f8f1ff9da8f5a7e98348f460d223de1/lld/COFF/Driver.cpp#L2044-L2048) ``` if (config->min

[Bug ld/32264] For Windows,`.CRT` section should be merged into `.rdata`

2024-10-11 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32264 --- Comment #1 from LIU Hao --- The special case in LLD is here: (https://github.com/llvm/llvm-project/blob/ebeb56af5f8f1ff9da8f5a7e98348f460d223de1/lld/COFF/Writer.cpp#L1113-L1123) ```c++ if (name == ".CRT") { // In link.exe, there

[Bug ld/32264] New: For Windows, `.CRT` section should be merged into `.rdata`

2024-10-10 Thread lh_mouse at 126 dot com
Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: lh_mouse at 126 dot com Target Milestone: --- This program (https://godbolt.org/z/rsoW7vKd8) ``` #include volatile int value __attribute__((__section__(".CRT")))

[Bug ld/31720] LD segfaults randomly when building GCC on i686-w64-mingw32

2024-05-13 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31720 LIU Hao changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED

[Bug ld/31720] LD segfaults randomly when building GCC on i686-w64-mingw32

2024-05-09 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31720 LIU Hao changed: What|Removed |Added Build||i686-w64-mingw32 Host|

[Bug ld/31720] New: LD segfaults randomly when building GCC on i686-w64-mingw32

2024-05-09 Thread lh_mouse at 126 dot com
Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: lh_mouse at 126 dot com Target Milestone: --- bootstrapping GCC 14.1 on i686-w64-mingw32 fails randomly; running the offending commands by hand does not fail: ``` /home/lh_mouse

[Bug gas/31092] SECREL32 produces wrong value on x86_64-w64-mingw32

2023-11-28 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31092 LIU Hao changed: What|Removed |Added Target||x86_64-w64-mingw32 -- You are receiving th

[Bug gas/31092] New: SECREL32 produces wrong value on x86_64-w64-mingw32

2023-11-28 Thread lh_mouse at 126 dot com
Component: gas Assignee: unassigned at sourceware dot org Reporter: lh_mouse at 126 dot com Target Milestone: --- C source: ``` int printf(const char*, ...) __attribute__((__dllimport__)); void exit(int) __attribute__((__noreturn__, __dllimport__)); __thread int my_value = 42

[Bug ld/30421] Symbols in import lib are influenced by .def file

2023-05-14 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30421 --- Comment #4 from LIU Hao --- >From binutils/MAINTAINERS: ``` The home page for binutils is: http://www.gnu.org/software/binutils/binutils.html and patches should be sent to: binut...@sourceware.org ``` -- You are receiving this

[Bug binutils/30421] Symbols in import lib are influenced by .def file

2023-05-04 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30421 LIU Hao changed: What|Removed |Added CC||lh_mouse at 126 dot com -- You are

[Bug gas/30418] use of labels that happen to match register names or keywords

2023-05-03 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30418 LIU Hao changed: What|Removed |Added Target|x86-64-*-* |x86_64-*-* -- You are receiving this mail

[Bug gas/30418] use of labels that happen to match register names or keywords

2023-05-03 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30418 --- Comment #2 from LIU Hao --- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109726 -- You are receiving this mail because: You are on the CC list for the bug.

[Bug gas/30418] use of labels that happen to match register names or keywords

2023-05-03 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30418 LIU Hao changed: What|Removed |Added CC||hjl.tools at gmail dot com --- Comment #1 f

[Bug gas/30418] use of labels that happen to match register names or keywords

2023-05-03 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30418 LIU Hao changed: What|Removed |Added See Also||https://sourceware.org/bugz

[Bug gas/30418] New: use of labels that happen to match register names or keywords

2023-05-03 Thread lh_mouse at 126 dot com
: normal Priority: P2 Component: gas Assignee: unassigned at sourceware dot org Reporter: lh_mouse at 126 dot com Target Milestone: --- Possible dup of https://sourceware.org/bugzilla/show_bug.cgi?id=12240 This is how MSVC handles such names: (https

[Bug gas/30336] The GNU Assembler has bugs in Intel syntax

2023-05-01 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30336 --- Comment #5 from LIU Hao --- There is apparently confusion about using register names, instruction names or other keywords as labels. People who write Intel assembly shall know that those are 'bad' names for labels. That is to say, expecti

[Bug gas/12240] offset can't be used as label in Intel syntax

2023-04-27 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=12240 LIU Hao changed: What|Removed |Added CC||lh_mouse at 126 dot com --- Comment #2

[Bug gas/30336] The GNU Assembler has bugs in Intel syntax

2023-04-27 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30336 LIU Hao changed: What|Removed |Added CC||lh_mouse at 126 dot com --- Comment #1

[Bug gas/29145] GAS always generates padding instructions regardless of `--no-pad-sections`

2022-06-12 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29145 --- Comment #6 from LIU Hao --- Is there any progress on this issue? If this behavior can't be changed by default, it's also nice to have an experimental option. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug gas/29145] GAS always generates padding instructions regardless of `--no-pad-sections`

2022-05-23 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29145 --- Comment #5 from LIU Hao --- On the page you've referenced, there is > 20 4 PointerToRawData > The file pointer to the first page of the section within the COFF file. > For executable images, this must be a multiple of FileAlignment from

[Bug gas/29145] GAS always generates padding instructions regardless of `--no-pad-sections`

2022-05-23 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29145 --- Comment #4 from LIU Hao --- Sent: https://cygwin.com/pipermail/cygwin/2022-May/251509.html -- You are receiving this mail because: You are on the CC list for the bug.

[Bug gas/29145] GAS always generates padding instructions regardless of `--no-pad-sections`

2022-05-18 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29145 --- Comment #2 from LIU Hao --- (In reply to Nick Clifton from comment #1) > (In reply to LIU Hao from comment #0) > > > We attempt to compile the same code targeting mingw-w64: > > > This time the `.text` section has a size of 16 and alig

[Bug gas/29145] GAS always generates padding instructions regardless of `--no-pad-sections`

2022-05-13 Thread lh_mouse at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29145 LIU Hao changed: What|Removed |Added Target||x86_64-w64-mingw32 -- You are receiving th

[Bug gas/29145] New: GAS always generates padding instructions regardless of `--no-pad-sections`

2022-05-13 Thread lh_mouse at 126 dot com
Severity: normal Priority: P2 Component: gas Assignee: unassigned at sourceware dot org Reporter: lh_mouse at 126 dot com Target Milestone: --- Given this simple C program: ``` int foo(int a); int bar(int a) { return foo(a); } ``` We compile it with GCC