[Bug ld/23762] __CTOR_LIST__ should be aligned at 4 bytes for i686-windows-mingw32
https://sourceware.org/bugzilla/show_bug.cgi?id=23762 --- Comment #1 from Martin Storsjö --- While the conclusion probably is right, I'd like to see more details about why this happens in this configuration and why it hasn't happened so far. As far as I can see, ld places __CTOR_LIST__ directly at the end of the .text section - and in case the .text section isn't exactly a multiple of 4, the -1 at the beginning would be unaligned, and there would be garbage/fillers between that and the first member from .ctors (which is aligned) - is this what is happening? Then why does this not happen in normal setups with GCC, since GCC also does align the .ctors pointers to 4 bytes? -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug ld/23762] New: __CTOR_LIST__ should be aligned at 4 bytes for i686-windows-mingw32
https://sourceware.org/bugzilla/show_bug.cgi?id=23762 Bug ID: 23762 Summary: __CTOR_LIST__ should be aligned at 4 bytes for i686-windows-mingw32 Product: binutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: pirama at google dot com CC: martin at martin dot st Target Milestone: --- This seems to be fine until now but the combination of clang + libc++ + MinGW causes issues where __CTOR_LIST__ is not aligned at 4 bytes, causing garbage after the -1 at the beginning. This seems like a safe change considering that __CTOR_LIST__ is aligned to 8 bytes for 64-bit (ld/scripttempl/pep.sc). I can try to find a reduced test case if not. (If there're instructions on how to submit a patch, I'm happy to send one). -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug ld/19011] Issues with ld on mingw-w64 and bad defaults
https://sourceware.org/bugzilla/show_bug.cgi?id=19011 --- Comment #8 from gerald at wireshark dot org --- Googling for "mingw-w64 aslr" turned up a CERT vulnerability note[1] for this issue along with CVE-2018-5392. It wasn't apparent from the VN or the CVE whether or not Sourceware had been notified of the CVE assignment. [1] https://www.kb.cert.org/vuls/id/307144 -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug ld/19011] Issues with ld on mingw-w64 and bad defaults
https://sourceware.org/bugzilla/show_bug.cgi?id=19011 --- Comment #7 from Tom Ritter --- This is a big drive-by, as I don't have much understanding on the details of the problem; but Tor uses the following patch to add a relocation section so Windows builds of Tor Browser can have ASLR: https://gitweb.torproject.org/builders/tor-browser-build.git/tree/projects/binutils/enable-reloc-section-ld.patch -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug admin/23759] Qimak
https://sourceware.org/bugzilla/show_bug.cgi?id=23759 Alan Modra changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Alan Modra --- Spam -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug admin/23759] New: Qimak
https://sourceware.org/bugzilla/show_bug.cgi?id=23759 Bug ID: 23759 Summary: Qimak Product: binutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: admin Assignee: unassigned at sourceware dot org Reporter: Romilala123 at gmail dot com Target Milestone: --- Created attachment 11314 --> https://sourceware.org/bugzilla/attachment.cgi?id=11314=edit RomyGansTq Nahcottt -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
