[Bug ld/31503] [hppa] Unsupported 14-bit PA 2.0 relocations for 32-bit (narrow) mode (elf32-hppa.c)

2024-03-29 Thread danglin at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=31503

John David Anglin  changed:

   What|Removed |Added

  Attachment #15439|0   |1
is obsolete||

--- Comment #12 from John David Anglin  ---
Created attachment 15446
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15446=edit
Patch

Fixes alignment of .data.

Maybe the alignment for .data could be done in elf.sc so a new script
isn't required?

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


[Bug binutils/31457] strip: SEGV in copy_archive

2024-03-29 Thread chkunq at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31457

Driller SE  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |NOTABUG

--- Comment #4 from Driller SE  ---
Mark this issue as NOTABUG

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


[Bug binutils/31457] strip: SEGV in copy_archive

2024-03-29 Thread chkunq at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31457

--- Comment #3 from Driller SE  ---
After a thorough reproduction process, I've come to the conclusion that this is
a false positive caused by my oversight, for which I apologize for any
inconvenience caused. 

Below is an explanation of the false positive, along with the relevant code:
```c
output_element = bfd_openr (output_name, output_target);
ptr = _element->archive_next;
*ptr = NULL;
```
The false positive occurred because:

During my testing of strip-new, I manually deleted the directory containing
file`output_name` (before strip could automatically delete it), resulting in
`bfd_openr` returning NULL to `output_element`, which then led to a SEGV at
`*ptr = NULL`.

Therefore, this problem would not occur under non-contrived circumstances
(i.e., if the temporary directories were not manually deleted before strip
automatically deletes them).

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