[Bug ld/32896] GNU ld does not enforce PT_TLS segment p_offset/p_vaddr congruity with p_align

2025-04-23 Thread mmalcomson at nvidia dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32896

--- Comment #1 from Matthew Malcomson  ---
Created attachment 16045
  --> https://sourceware.org/bugzilla/attachment.cgi?id=16045&action=edit
WIP-patch-for-comment

Adding a WIP patch that is at least passing this testcase.

Mostly I'm attaching this hoping that someone could comment on whether it's
going in the right lines.  Main questions that I'm looking to answer are:

1) Adjusting the p_filesz and p_memsz manually to account for any padding. 
This ends up with padding in both the file and the VMA.
2) Is there any other clause somewhere later in the file that I could merge
with?  There are a bunch of clauses that *seem* promising but I couldn't quite
make sure they fit.
3) I expect that I can't use `vma_page_aligned_bias` based on the section as
I'm doing in this patch but instead have to find the total PT_TLS alignment
that is needed -- in case the user used some linker script that puts the .tbss
before the .tdata section.  Does that sound right?  In that case it seems a
little restructuring would be worthwhile.

Any other corrections / extra information would be welcome.

Also any high-level description of the requirements here would be welcome --
I'm slowly getting to grips with it but could easily be missing something.

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


[Bug ld/32603] ld segv in bfd_set_format with -w -o XXX and no permissions for XXX

2025-04-23 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=32603

--- Comment #15 from Sourceware Commits  ---
The binutils-2_44-branch branch has been updated by Alan Modra
:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=fe459e33c676883b5f28cc96c00e242973d906a9

commit fe459e33c676883b5f28cc96c00e242973d906a9
Author: Alan Modra 
Date:   Thu Apr 24 10:01:29 2025 +0930

PR 32603, revert message changes in 0b7f992b78fe and 31e9e2e8d109

This puts back %F into translated fatal error messages (and reverts a
few other small changes), to not disturb translation work done for the
2.44 branch.

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


[Bug ld/26815] Unnecessary error on linking STV_PROTECTED library: relocation R_X86_64_PC32 against protected symbol `f' can not be used when making a shared object

2025-04-23 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=26815

Sam James  changed:

   What|Removed |Added

 CC||sam at gentoo dot org
 Resolution|--- |FIXED
   See Also||https://gcc.gnu.org/bugzill
   ||a/show_bug.cgi?id=19520,
   ||https://gcc.gnu.org/bugzill
   ||a/show_bug.cgi?id=98112
 Status|WAITING |RESOLVED

--- Comment #11 from Sam James  ---
(In reply to Thiago Macieira from comment #10)
> (In reply to H.J. Lu from comment #9)
> > Should this be closed by -mno-direct-extern-access change in GCC?
> 
> Yes.
> 
> making that the default and getting rid of copy relocations would be better,
> though.

Closing.

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


[Bug ld/30144] LD --entry does not accept function name

2025-04-23 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30144

--- Comment #7 from Nick Clifton  ---
Created attachment 16041
  --> https://sourceware.org/bugzilla/attachment.cgi?id=16041&action=edit
Proposed patch

Hi Pali,

  The secret is to add a new emulation function.  These functions are target
specific, so in that way you can make sure that the new code is only used for
x86 targets.

  Please try out this revised version of your patch to see what I mean.  I have
not actually tested it, but I think that it should work... :-)

  Currently the new code is enabled both for 32-bit and 64-bit x86/x86_64
architectures.  If it should be restricted to just 32-bits then you should be
able to add a "case x${OUTPUT_FORMAT} in" controlling clause, as is done for
other functions in the elf-x86.em file.

  If this patch is OK, please let me know and I will commit it.  Otherwise
please feel free to amend it as needed.

Cheers
  Nick

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


[Bug ld/27871] ld: Add -Bsymbolic-non-weak-functions which only applies to STB_GLOBAL STT_FUNC

2025-04-23 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=27871

Sam James  changed:

   What|Removed |Added

 CC||sam at gentoo dot org
   See Also||https://gcc.gnu.org/bugzill
   ||a/show_bug.cgi?id=100593

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


[Bug ld/30144] LD --entry does not accept function name

2025-04-23 Thread pali at kernel dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30144

Pali Rohár  changed:

   What|Removed |Added

  Attachment #16036|0   |1
is obsolete||

--- Comment #8 from Pali Rohár  ---
Created attachment 16046
  --> https://sourceware.org/bugzilla/attachment.cgi?id=16046&action=edit
Updated patch

Hello Nick, thank you for your input. It really helped me.

I did following modifications to your proposed patch:
- Put implementation into the pe.em instead of elf-x86.em
- Directly address symbol mangling for the chosen DLL or driver build for i386
- Rename callback function to find_alt_start_symbol and drop its info argument
- Update documentation

The updated version is attached. I tested it and works fine for me.

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