[Bug ld/28709] [RISC-V] a unused section can't be removed with -gc-sections

https://sourceware.org/bugzilla/show_bug.cgi?id=28709 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=443aa5f05edb58fc1774f926e9259b7c5a180926 commit 443aa5f05edb58fc1774f926e9259

[Bug ld/28709] [RISC-V] a unused section can't be removed with -gc-sections

https://sourceware.org/bugzilla/show_bug.cgi?id=28709 --- Comment #7 from lifang_xia at linux dot alibaba.com --- Thank you so much for explaining that. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/28141] support a small discontiguous stack for goroutines

https://sourceware.org/bugzilla/show_bug.cgi?id=28141 --- Comment #6 from dilyan.palauzov at aegee dot org --- > but given that it is specific to gccgo and not needed by the, umm, non-gcc go > compiler My understanding is that this can be used by any language, whenever -fsplit-stack - https://g

readelf: also dump the address contained in offset on R_386_RELATIVE relocs

I see that, when dumping R_386_RELATIVE relocs in readelf, the format is like this Offset InfoTypeSym.Value Sym. Name 3d01 0008 R_386_RELATIVE If I understand that type of relocation correctly, another information is missing: the address contained at the g

Issue 40362 in oss-fuzz: binutils:fuzz_as: Integer-overflow in next_char_of_string

Updates: Labels: -restrict-view-commit Comment #5 on issue 40362 by sheriffbot: binutils:fuzz_as: Integer-overflow in next_char_of_string https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40362#c5 This bug has been fixed. It has been opened to the public. - Your friendly Sheriffbot