[Bug ld/30359] Create Resource-Only DLL

2023-05-16 Thread pali at kernel dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #17 from Pali Rohár --- Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/30359] Create Resource-Only DLL

2023-05-16 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #16 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d1792f72bf92ac06be7a4785567e2c7bf78c0496 commit d1792f72bf92ac06be7a478556

[Bug ld/30359] Create Resource-Only DLL

2023-05-16 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #15 from Nick Clifton --- (In reply to Pali Rohár from comment #14) > Well, if this is the way how it should be used then "fixed" linker script > should be distributed with linker. Or at least described in the LD > documentation. B

[Bug ld/30359] Create Resource-Only DLL

2023-05-10 Thread pali at kernel dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #14 from Pali Rohár --- Well, if this is the way how it should be used then "fixed" linker script should be distributed with linker. Or at least described in the LD documentation. Because it is really hard to find some information

[Bug ld/30359] Create Resource-Only DLL

2023-05-09 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 Nick Clifton changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug ld/30359] Create Resource-Only DLL

2023-05-08 Thread pali at kernel dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #12 from Pali Rohár --- This new linker script works fine. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/30359] Create Resource-Only DLL

2023-05-04 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #11 from Nick Clifton --- Created attachment 14861 --> https://sourceware.org/bugzilla/attachment.cgi?id=14861&action=edit Example linker script Hi Pali, OK, so the problem was the linker script that I was using, which was

[Bug ld/30359] Create Resource-Only DLL

2023-05-03 Thread pali at kernel dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #10 from Pali Rohár --- Checking IMAGE_SCN_MEM_DISCARDABLE is not a good idea too as this section is still loaded from .sys drivers and discarded after driver is initialized. -- You are receiving this mail because: You are on the

[Bug ld/30359] Create Resource-Only DLL

2023-04-26 Thread pali at kernel dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #9 from Pali Rohár --- That check s_size != 0 does not really look good. I have quickly scanned wine and reactos source codes and seems that they require non-zero VMA addresses for resources. Maybe another check could be based on e

[Bug ld/30359] Create Resource-Only DLL

2023-04-26 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #8 from Nick Clifton --- (In reply to Pali Rohár from comment #6) Hi Pali, > And then somehow put > > LONG (-1); LONG (-1); > > only if _LENGTH_OF_DATA_ is non-zero. > > This is also not possible by linker script language? Be

[Bug ld/30359] Create Resource-Only DLL

2023-04-25 Thread pali at kernel dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #7 from Pali Rohár --- Or maybe instead of "if (scnhdr_int->s_vaddr != 0)" it should be "#ifdef COFF_IMAGE_WITH_PE"? -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/30359] Create Resource-Only DLL

2023-04-25 Thread pali at kernel dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #6 from Pali Rohár --- (In reply to Nick Clifton from comment #5) > (In reply to Pali Rohár from comment #4) > > > > These markers are used by the execution startup code to help find the two > > > tables. > > > > I see... But in

[Bug ld/30359] Create Resource-Only DLL

2023-04-25 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #5 from Nick Clifton --- (In reply to Pali Rohár from comment #4) > > These markers are used by the execution startup code to help find the two > > tables. > > I see... But in this case there is nothing in .text section, just tho

[Bug ld/30359] Create Resource-Only DLL

2023-04-21 Thread pali at kernel dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #4 from Pali Rohár --- (In reply to Nick Clifton from comment #3) > (In reply to Pali Rohár from comment #2) > > If adding empty import table and something in code .text sections is feature > > of the linker, it is somewhere docume

[Bug ld/30359] Create Resource-Only DLL

2023-04-19 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #3 from Nick Clifton --- (In reply to Pali Rohár from comment #2) > If adding empty import table and something in code .text sections is feature > of the linker, it is somewhere documented? No. :-( > What it is doing and what is

[Bug ld/30359] Create Resource-Only DLL

2023-04-18 Thread pali at kernel dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #2 from Pali Rohár --- If adding empty import table and something in code .text sections is feature of the linker, it is somewhere documented? What it is doing and what is putting there (as those sections are not in any user suppli

[Bug ld/30359] Create Resource-Only DLL

2023-04-18 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #1