[Bug target/24842] testsuite failure: gcc.dg/attr-weakref-1.c execution test

[Bug target/24842] testsuite failure: gcc.dg/attr-weakref-1.c execution test

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24842

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2012-01-11
     Ever Confirmed|0                           |1

--- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-11 14:52:40 UTC ---
Is this still an issue?

[Bug target/24842] testsuite failure: gcc.dg/attr-weakref-1.c execution test

[pinskia at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24842

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
No feedback in over a year so closing.

[Bug target/24842] testsuite failure: gcc.dg/attr-weakref-1.c execution test

[hp at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24842

Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |NEW
         Resolution|FIXED                       |---

--- Comment #7 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #6)
> No feedback in over a year so closing.

Sorry I forgot to follow-up.  The problem is still there as of r204654.

[Bug target/24842] testsuite failure: gcc.dg/attr-weakref-1.c execution test

[hp at gcc dot gnu dot org]

------- 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 the test that failed,
without looking at the simulator trace of course, which I'll do when I get to
looking at this myself.  (Which anyone can do anyway before that; just install
the simulator and start printf-ing.)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24842

[Bug target/24842] testsuite failure: gcc.dg/attr-weakref-1.c execution test

[aoliva at gcc dot gnu dot org]

------- 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 weak symbols properly, unless there's something very peculiar
about the way this target handles weak symbols.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24842

[Bug target/24842] testsuite failure: gcc.dg/attr-weakref-1.c execution test

[hp at gcc dot gnu dot org]

------- 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's way of telling this).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24842

[Bug target/24842] testsuite failure: gcc.dg/attr-weakref-1.c execution test

[aoliva at gcc dot gnu dot org]

------- 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 minute whether to
issue a .weak directive for the target or not.

Will you please let me know what the excess errors are that you get, so that I
can decide whether to delve into the issue myself or not?  Thanks,


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24842