http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24842
Hans-Peter Nilsson changed:
What|Removed |Added
Status|RESOLVED|NEW
Resolution|FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24842
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24842
Richard Guenther changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
--- Comment #4 from hp at gcc dot gnu dot org 2005-11-29 14:08 ---
Yes, it may be a linker error. This target uses the generic linker machinery
(since linking from ELF to mmo), which is not exactly the hot-path for other
targets.
I know of no particular way of telling *which* part of t
--- Comment #3 from aoliva at gcc dot gnu dot org 2005-11-29 13:50 ---
Sorry, I totally misread the testsuite output.
Can you tell what part of the execution test that fails? I find it very
unlikely that this is a compiler error; it's far more likely to be a linker
failure to handle we
--- Comment #2 from hp at gcc dot gnu dot org 2005-11-14 18:35 ---
In response to comment #1 regarding "excess errors", see the original
description: I don't get any, I just get a call to abort when the
test-program is executed (as you know, the "*** EXIT code 4242" is
the status-wrapper
--- Comment #1 from aoliva at gcc dot gnu dot org 2005-11-14 15:41 ---
Yeah, weakref support in the compiler is independent of .weakref support in the
assembler. If .weakref is not available, the compiler will emulate that by
always using the target symbol name, and deciding at the last
