[Bug ld/18963] Addition is not commutative

2020-04-20 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=18963

--- Comment #18 from Nick Clifton  ---
(In reply to Stephen Casner from comment #17)

> Please quantify how much disk space and time is required for the testing.

Since you ask - my toolchains occupy 106Gb of disk space and it takes 2-3 hours
to rebuild and rerun the testsuites.  I do this each day - whilst reading my
email - in order to help catch patches that introduce new failures.

Cheers
  Nick

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


[Bug binutils/25828] nm for pdp11-aout shows symbols undefined or sign-extended to 64 bits

2020-04-20 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=25828

--- Comment #4 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=23c8270e9dc60bb78c1800b7deedc117efdb9e92

commit 23c8270e9dc60bb78c1800b7deedc117efdb9e92
Author: Stephen Casner 
Date:   Mon Apr 20 12:49:50 2020 +0100

When bfd/pdp11.c was copied from bfd/aoutx.h, the #defines for external
symbol types N_TEXT etc. were #undef'd and then #define'd with new values.  But
N_STAB was not changed even though the new value for N_EXT overlapped with it. 
This caused aout_link_write_symbols() to treat global symbols referenced in the
source but defined in a linker script as undefined.

Separately, in translate_symbol_table() the 16-bit symbol values were sign
extended to unsigned long (e.g., 64 bits) when they really should be treated as
unsigned so the value remains 16 bits.

PR 25828
* pdp11.c (N_STAB): Modify value to avoid conflict with N_EXT
causing globals from linker script to be treated as debug symbols.
(translate_symbol_table): Don't sign-extend symbol values from 16
to 64 bits in nm output.

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


[Bug binutils/25828] nm for pdp11-aout shows symbols undefined or sign-extended to 64 bits

2020-04-20 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=25828

Nick Clifton  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from Nick Clifton  ---
Hi Stephen,

  Sorry about that.  The patch is now applied.

Cheers
  Nick

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


[Bug ld/25829] Several ld tests fail for 16-bit targets like pdp11-aout

2020-04-20 Thread casner at acm dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=25829

--- Comment #2 from Stephen Casner  ---
Does this patch also cause some of the other targets' testsuites to fail? 
Scaling addresses down should not cause a problem, but if support for .dc.a is
not universal that could be a problem.

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


[Bug gas/25406] [ARM] pcrel relocations referencing STB_GLOBAL symbols are resolved at assembly time

2020-04-20 Thread tnfchris at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=25406

--- Comment #4 from Tamar Christina  ---
(In reply to Fangrui Song from comment #3)
> Alternatively, we can reject such non-STB_LOCAL labels when they may be
> preemptible. The scheme will still be consistent with the rest of ELF models
> and architectures.

Wouldn't this then not accomplish what you wanted initially which was make them
pre-emptible?

Following the LLVM discussion it seems they have decided to leave it as is for
Arm but not revert the Thumb patch that made them pre-emptible.

That seems a bit arbitrary.. 

As far as I can tell the ELF standard says it "can" be pre-empted, not that it
must be.  And with such small ranges is there an actual use case for them to
be?

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


[Bug ld/24673] [RISCV] -fPIC -pie and -fPIC -no-pie create unexpected R_RISCV_NONE R_RISCV_DTPMOD64 relocations

2020-04-20 Thread raj.khem at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24673

Khem Raj  changed:

   What|Removed |Added

 CC||raj.khem at gmail dot com

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


[Bug ld/24676] [RISCV] Redundant R_RISCV_DTPMOD* R_RISCV_DTPREL* resulted from Global Dynamic -> Local Exec relaxation

2020-04-20 Thread raj.khem at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24676

Khem Raj  changed:

   What|Removed |Added

 CC||raj.khem at gmail dot com

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


[Bug ld/24676] [RISCV] Redundant R_RISCV_DTPMOD* R_RISCV_DTPREL* resulted from Global Dynamic -> Local Exec relaxation

2020-04-20 Thread raj.khem at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24676

--- Comment #2 from Khem Raj  ---
I am seeing bunch of packages which are showing the R_RISCV_NONE issue

For detail list see the do_package_qa failures here [1]

[1] http://errors.yoctoproject.org/Errors/Build/101576/

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