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

2021-12-28 Thread sheriffbot via monorail
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

-- 
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.

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

2021-12-28 Thread Andrea Monaco


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 given offset, which ld.so adds
to the load address of the module and then overwrites at the same
offset.

I think it is reasonable to provide that information.  Some users might
need it for debugging or learning purposes.



Thanks,

Andrea Monaco



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

2021-12-28 Thread dilyan.palauzov at aegee dot org
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://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html#index-fsplit-stack
- is passed to gcc.  So it is not specific to gccgo, but to any multi-threaded
program.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


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

2021-12-28 Thread lifang_xia at linux dot alibaba.com
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/28709] [RISC-V] a unused section can't be removed with -gc-sections

2021-12-28 Thread cvs-commit at gcc dot gnu.org
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 443aa5f05edb58fc1774f926e9259b7c5a180926
Author: Alan Modra 
Date:   Tue Dec 21 01:09:13 2021 +1030

gas reloc sorting

In some cases, eg. riscv_pre_output_hook, gas generates out-of-order
relocations.  Various places in the linker assume relocs are sorted
by increasing r_offset, which is normally the case.  Provide
GAS_SORT_RELOCS to handle unsorted relocs.

bfd/
PR 28709
* elf32-nds32.c (nds32_insertion_sort): Make static.
* elf32-nds32.h (nds32_insertion_sort): Delete declaration.
gas/
PR 28709
* write.c (write_relocs): Implement reloc sorting by r_offset
when GAS_SORT_RELOCS.
* config/tc-nds32.c (compar_relent, nds32_set_section_relocs):
Delete.
* config/tc-nds32.h (nds32_set_section_relocs): Don't declare.
(SET_SECTION_RELOCS): Don't define.
(GAS_SORT_RELOCS): Define.
* config/tc-riscv.h (GAS_SORT_RELOCS): Define.

-- 
You are receiving this mail because:
You are on the CC list for the bug.