[Bug ld/46] ld testsuite failure on cygwin: FAIL: cdtest with -Ur

2019-11-20 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=46

Alan Modra  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|unassigned at sources dot redhat.c |amodra at gmail dot com
   |om  |

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


[Bug gprof/114] gprof --line takes a very, very, VERY long time

2019-11-20 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=114

Alan Modra  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #7 from Alan Modra  ---
I'm going to close this as wontfix since no one has cared enough in 15 years to
write a patch that doesn't introduce correctness issues.

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


[Bug ld/25210] aarch64: -fix-cortex-a53-835769 --fix-cortex-a53-843419 lead to invalid operation

2019-11-20 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=25210

Alan Modra  changed:

   What|Removed |Added

 CC||amodra at gmail dot com

--- Comment #2 from Alan Modra  ---
> ./ld-new: linker stubs: file class ELFCLASSNONE incompatible with ELFCLASS64

See bfd/elf64ppc.c ppc64_elf_init_stub_bfd.  elf64-ppc.c size_stubs avoids
looking at the stub bfd by excluding any bfd with symtab_hdr->sh_info zero.  No
symbols, not even locals, is generally an uninteresting file.

Also, I'd say elfNN_aarch64_size_stubs ought to be checking that the input bfds
are aarch64-elf.

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


[Bug ld/25205] relocation truncated to fit: R_RISCV_JAL against undefined symbol `pthread_once'

2019-11-20 Thread sch...@linux-m68k.org
https://sourceware.org/bugzilla/show_bug.cgi?id=25205

--- Comment #1 from Andreas Schwab  ---
Full build log:
https://build.opensuse.org/package/live_build_log/home:Andreas_Schwab:Factory/llvm10/r/riscv64

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


[Bug ld/25210] aarch64: -fix-cortex-a53-835769 --fix-cortex-a53-843419 lead to invalid operation

2019-11-20 Thread matz at suse dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=25210

--- Comment #1 from Michael Matz  ---
FWIW, master still has the same problem and the same patch helps.

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


[Bug ld/25210] New: aarch64: -fix-cortex-a53-835769 --fix-cortex-a53-843419 lead to invalid operation

2019-11-20 Thread matz at suse dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=25210

Bug ID: 25210
   Summary: aarch64: -fix-cortex-a53-835769
--fix-cortex-a53-843419 lead to invalid operation
   Product: binutils
   Version: 2.33
Status: NEW
  Severity: normal
  Priority: P2
 Component: ld
  Assignee: unassigned at sourceware dot org
  Reporter: matz at suse dot de
  Target Milestone: ---

This came up in our distro build when updating to binutils 2.33 (2.32 was still
fine) which then fails building GCC.  But it can actually be reproduced by
the testcases included in binutils itself, when using both fix-arrata options
at the same time:

(on an aarch64 system, from a binutils checkout 2.33 branch):
% ../configure --disable-gold; make CFLAGS=-g -j8
% cd ld
% gcc -c -o bla.o ../../ld/testsuite/ld-aarch64/erratum835769.s
% ld bla.o
ld: warning: cannot find entry symbol _start; defaulting to 00400078
(i.e. works)
% ./ld-new --fix-cortex-a53-835769 --fix-cortex-a53-843419=full bla.o
./ld-new: can not size stub section: invalid operation
./ld-new: warning: cannot find entry symbol _start; defaulting to
00400078
./ld-new: linker stubs: file class ELFCLASSNONE incompatible with ELFCLASS64
./ld-new: final link failed: file in wrong format

This might be related to the fix for PR24373, as that seems the only relevant
change re linker stubs on aarch64 between 2.32 and 2.33.  I haven't checked if
master has the same problem.

I've debugged this a little bit, and the error happens because
elf64_aarch64_size_stubs iterates over all input_bfds, and over all sections
and tries to determine if it needs the fixes; while doing so it calls (of
course) bfd_malloc_and_get_section, which breaks because one of the input bfds
doesn't have an iovec.  This bfd is precisely the one created for the stubs.
So the iteration over all input BFDs is confused when it inspects the stub_bfd
for needing stubs.  I.e. this patch helps the immediate cause:

--- ../../bfd/elfnn-aarch64.c.mm2019-09-09 13:19:43.0 +
+++ ../../bfd/elfnn-aarch64.c   2019-11-20 11:44:00.0 +
@@ -4312,7 +4312,8 @@ elfNN_aarch64_size_stubs (bfd *output_bf

   for (input_bfd = info->input_bfds;
   input_bfd != NULL; input_bfd = input_bfd->link.next)
-   if (!_bfd_aarch64_erratum_835769_scan (input_bfd, info,
+   if (input_bfd != stub_bfd
+   && !_bfd_aarch64_erratum_835769_scan (input_bfd, info,
   &num_erratum_835769_fixes))
  return FALSE;

@@ -4327,6 +4328,7 @@ elfNN_aarch64_size_stubs (bfd *output_bf
   for (input_bfd = info->input_bfds;
   input_bfd != NULL;
   input_bfd = input_bfd->link.next)
+   if (input_bfd != stub_bfd)
{
  asection *section;

But I'm not sure if this is complete, or the correct place; or if perhaps the
check should be based on sections being linker created, though I think the
above is better.

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


[Bug gas/24944] gas doesn't read all necessary digits when parsing a floating point number

2019-11-20 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=24944

--- Comment #2 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=94c9b9db4b689bc1ae643e053580db1fdfaee2d4

commit 94c9b9db4b689bc1ae643e053580db1fdfaee2d4
Author: Alan Modra 
Date:   Wed Nov 20 21:54:07 2019 +1030

PR24944, gas doesn't read enough digits when parsing a floating point
number

PR 24944
* atof-generic.c (atof_generic): Increase decimal guard digits.
* testsuite/gas/i386/fp.s: Add more tests.
* testsuite/gas/i386/fp.d: Update.

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


[Bug gas/24944] gas doesn't read all necessary digits when parsing a floating point number

2019-11-20 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24944

Alan Modra  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
   Target Milestone|--- |2.34

--- Comment #3 from Alan Modra  ---
Fixed.

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


[Bug binutils/25120] Portability issues in binutils 2.33 due to libctf

2019-11-20 Thread nick.alcock at oracle dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=25120

--- Comment #12 from Nick Alcock  ---
Thanks! I already have that locally -- I really should finish testing and
submit everything.

Simply removing __thread won't do, unfortunately: it makes libctf even less
threadsafe than it already is, and I'm trying to get it *more* threadsafe. The
only thing that's held me off fixing this bug (other than pressure of other
work, like the deduplicating CTF linker) is the annoyance of having to
implement bsearch_r :) but I suppose I can take the bsearch from glibc without
worries.

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


[Bug gas/24944] gas doesn't read all necessary digits when parsing a floating point number

2019-11-20 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24944

Alan Modra  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
   Last reconfirmed||2019-11-20
   Assignee|unassigned at sourceware dot org   |amodra at gmail dot com
Summary|gas doesn't read all|gas doesn't read all
   |necessary ditits when parse |necessary digits when
   |a floating point number |parsing a floating point
   ||number
 Ever confirmed|0   |1

--- Comment #1 from Alan Modra  ---
Doing away with the limit won't work if someone uses .double with more than
1292 digits, because the following multiplication will overflow:
  more_than_enough_bits_for_digits
= (number_of_digits_to_use * 3321928 / 100 + 1);

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