[Bug ld/26681] The section flag 'o' doesn't work on NOTE section

2020-10-02 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=26681

--- Comment #1 from cvs-commit at gcc dot gnu.org  ---
The master branch has been updated by Nick Clifton :

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

commit 7026832e52cff026f877616ac0033c7bb8d1df6f
Author: H.J. Lu 
Date:   Fri Oct 2 11:08:19 2020 +0100

Allow note sections to be discarded when they are linked to another
discarded secction.

PR 26681
bfd * elflink.c (bfd_elf_gc_sections): Do not arbitrarily keep note
sections which are linked to another section.

ld  * testsuite/ld-elf/pr26681.s: New test.
* testsuite/ld-elf/pr26681.d: New test driver.
* testsuite/ld-elf/pr26681.l: New test output.

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


[Bug ld/26681] The section flag 'o' doesn't work on NOTE section

2020-10-02 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26681

Nick Clifton  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #2 from Nick Clifton  ---
Hi H.J.

  Sorry - you were right and I was wrong.  I have applied your patch.

Cheers
  Nick

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


[Bug gas/26694] gas x86-32: "can't handle non absolute segment in `lcall'" (or `ljmp')

2020-10-02 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26694

H.J. Lu  changed:

   What|Removed |Added

 CC||hjl.tools at gmail dot com

--- Comment #2 from H.J. Lu  ---
(In reply to TK Chia from comment #1)
> Created attachment 12881 [details]
> Proposed patch
> 
> I have enclosed a proposed patch --- including test case changes, and
> possible gas/ChangeLog entry.
> 
> Thank you!

Please also include a linker testcase to show that the final binary is correct.

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


[Bug gas/26694] gas x86-32: "can't handle non absolute segment in `lcall'" (or `ljmp')

2020-10-02 Thread u1049321969 at caramail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26694

--- Comment #3 from TK Chia  ---
(In reply to H.J. Lu from comment #2)

> Please also include a linker testcase to show that the final binary is
> correct.

May I know where the test case should go within the source tree?

Thank you!

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


[Bug gas/26694] gas x86-32: "can't handle non absolute segment in `lcall'" (or `ljmp')

2020-10-02 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26694

--- Comment #4 from H.J. Lu  ---
(In reply to TK Chia from comment #3)
> (In reply to H.J. Lu from comment #2)
> 
> > Please also include a linker testcase to show that the final binary is
> > correct.
> 
> May I know where the test case should go within the source tree?
> 
> Thank you!

You need to test both i386 and x86-64.  Linker tests should go into
ld/testsuite/ld-x86-64 and ld/testsuite/ld-i386.  Please also check
for linker overflow errors.

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


[Bug gas/26253] Support SHF_LINK_ORDER with sh_link=0

2020-10-02 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26253

Nick Clifton  changed:

   What|Removed |Added

 CC||nickc at redhat dot com

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

Hi Fangrui,

  Please could you try out the attached patch and see if it does what you
  expect.

Cheers
  Nick

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


[Bug gas/26253] Support SHF_LINK_ORDER with sh_link=0

2020-10-02 Thread i at maskray dot me
https://sourceware.org/bugzilla/show_bug.cgi?id=26253

--- Comment #3 from Fangrui Song  ---
(In reply to Nick Clifton from comment #2)
> Created attachment 12886 [details]
> Proposed patch
> 
> Hi Fangrui,
> 
>   Please could you try out the attached patch and see if it does what you
>   expect.
> 
> Cheers
>   Nick

Thanks, Nick! I have tested it on Linux x86-64.

LLVM's integrated assembler hard codes 0 but I think supporting other numerical
indexes is fine.

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


[Bug ld/26701] New: Ability to suppress warnings due to tags in a library

2020-10-02 Thread eyalroz at technion dot ac.il
https://sourceware.org/bugzilla/show_bug.cgi?id=26701

Bug ID: 26701
   Summary: Ability to suppress warnings due to tags in a library
   Product: binutils
   Version: unspecified
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: ld
  Assignee: unassigned at sourceware dot org
  Reporter: eyalroz at technion dot ac.il
  Target Milestone: ---

This is a generalization of bug 12017.

Compilers typically allow the user to suppress specific warnings, either
globally or locally at specific places in the code. 

Now, the linker apparently emits a warning when a symbol is used whose library
entry(/ies) indicate such a warning needs to be emitted. It should have an
option to suppress such warnings, in at least the following resolutions IMHO:

1. Globally
2. By (library, symbol name) pair
3. By library (e.g. glibc warnings)
4. By call site

Let's ignore (4.) for now because this is more complex and would require
compiler support for users to make work and focus on (1.)through (3.) . IIANM,
neither is currently possible with ld right now.

Now, (1.) should be really easy to implement; and (2.) and (3.) should not be
difficult to implement, and in a away such that the cost is minimal (e.g. have
a flag for whether _any_ specific suppressions are used, so when none are used
it's an extra flag check when having to emit a warning - a tolerable cost.)

If this were implemented, it would allow for an easy resolution of 12017.

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


[Bug ld/26701] Ability to suppress warnings due to tags in a library

2020-10-02 Thread eyalroz at technion dot ac.il
https://sourceware.org/bugzilla/show_bug.cgi?id=26701

Eyal Rozenberg  changed:

   What|Removed |Added

   See Also||https://sourceware.org/bugz
   ||illa/show_bug.cgi?id=12017

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


[Bug ld/26701] Ability to suppress warnings due to tags in a library

2020-10-02 Thread eyalroz at technion dot ac.il
https://sourceware.org/bugzilla/show_bug.cgi?id=26701

Eyal Rozenberg  changed:

   What|Removed |Added

   Severity|normal  |enhancement

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


[Bug ld/12017] Would like to disable compiler warning re use of tmpnam

2020-10-02 Thread eyalroz at technion dot ac.il
https://sourceware.org/bugzilla/show_bug.cgi?id=12017

Eyal Rozenberg  changed:

   What|Removed |Added

 CC||eyalroz at technion dot ac.il

--- Comment #7 from Eyal Rozenberg  ---
I've suggested an approach which would resolve this issue, as bug 26701 .

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


[Bug ld/26701] Ability to suppress warnings due to tags in a library

2020-10-02 Thread vampyrebat at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26701

Kib  changed:

   What|Removed |Added

 CC||vampyrebat at gmail dot com

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