[Bug target/33169] Compiler generates two different relocs for the same symbol

2007-10-22 Thread rsandifo at gcc dot gnu dot org
--- Comment #11 from rsandifo at gcc dot gnu dot org 2007-10-22 20:14 --- Aaron, Thanks for the testing. I've now applied the patch to the 4.2 branch. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33169

[Bug target/33169] Compiler generates two different relocs for the same symbol

2007-10-22 Thread rsandifo at gcc dot gnu dot org
--- Comment #10 from rsandifo at gcc dot gnu dot org 2007-10-22 20:11 --- Subject: Bug 33169 Author: rsandifo Date: Mon Oct 22 20:11:19 2007 New Revision: 129559 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=129559 Log: gcc/ PR target/33169 Backport from mainli

[Bug target/33169] Compiler generates two different relocs for the same symbol

2007-10-02 Thread atgraham at gmail dot com
--- Comment #9 from atgraham at gmail dot com 2007-10-03 05:31 --- The patch from Richard appears to fix the problem. With his patch applied, the compiler output is correct. -- atgraham at gmail dot com changed: What|Removed |Added ---

[Bug target/33169] Compiler generates two different relocs for the same symbol

2007-09-06 Thread rsandifo at gcc dot gnu dot org
--- Comment #8 from rsandifo at gcc dot gnu dot org 2007-09-06 18:25 --- Created an attachment (id=14164) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14164&action=view) The patch that I think fixed this on mainline This is a compiler bug rather than a linker bug. The compiler m

[Bug target/33169] Compiler generates two different relocs for the same symbol

2007-08-24 Thread atgraham at gmail dot com
--- Comment #7 from atgraham at gmail dot com 2007-08-24 16:34 --- binutils bug created: http://sourceware.org/bugzilla/show_bug.cgi?id=4959 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33169

[Bug target/33169] Compiler generates two different relocs for the same symbol

2007-08-24 Thread pinskia at gcc dot gnu dot org
--- Comment #6 from pinskia at gcc dot gnu dot org 2007-08-24 16:16 --- So one goes the GOT (the weakref) while the other does not (straight call). I am guess this is really a bug in binutils if a bug at all. Though two different relocs for the same symbol should be ok. >and thusly ch

[Bug target/33169] Compiler generates two different relocs for the same symbol

2007-08-24 Thread atgraham at gmail dot com
--- Comment #5 from atgraham at gmail dot com 2007-08-24 16:12 --- Created an attachment (id=14104) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14104&action=view) Output of "mipsel-linux-gcc -Os -s tworelocs.c" gcc output attached. -- http://gcc.gnu.org/bugzilla/show_bug.cg

[Bug target/33169] Compiler generates two different relocs for the same symbol

2007-08-24 Thread pinskia at gcc dot gnu dot org
--- Comment #4 from pinskia at gcc dot gnu dot org 2007-08-24 16:06 --- So what is happening is that you are using the function directly and also via a weakref. Can you give the output of GCC (that is the -S file)? This might be really a binutils bug. -- http://gcc.gnu.org/bugzill

[Bug target/33169] Compiler generates two different relocs for the same symbol

2007-08-24 Thread atgraham at gmail dot com
--- Comment #3 from atgraham at gmail dot com 2007-08-24 16:00 --- Here is a smaller bit of code for reproducing this problem. This doesn't depend on any C++. #include "pthread.h" static __typeof(pthread_mutex_lock) __gthrw_pthread_mutex_lock __attribute__ ((__weakref__("pthread_mutex_

[Bug target/33169] Compiler generates two different relocs for the same symbol

2007-08-24 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-08-24 09:23 --- MIPS-linux uses elf which has weak support. So I don't see why you think GTHREAD_USE_WEAK should not be defined. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added