--- Additional Comments From nickc at redhat dot com 2008-11-18 11:42
---
Created an attachment (id=3072)
-- (http://sourceware.org/bugzilla/attachment.cgi?id=3072action=view)
third try
--
What|Removed |Added
--- Additional Comments From nickc at redhat dot com 2008-11-18 11:45
---
Hi Rainer,
OK, I have uploaded a third patch for you to try. This one works(1) for me
although to be honest I do not really see how it is different from the second
patch. Anyway give it a whirl and see how
--- Additional Comments From ro at TechFak dot Uni-Bielefeld dot DE
2008-11-18 13:05 ---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC: could not
read symbols: Bad value
Hi Nick,
OK, I have uploaded a third patch for you to try. This one works(1) for me
Hi Rainer,
Unfortunately, regtesting the resulting GCC build is
currently hampered by the following warning:
/vol/gcc/obj/binutils-2.19.50-g/ld/ld-new: warning: section `.bss' type changed
to PROGBITS
This is harmless during the build, but many testcases (not only c++ and
libstdc++-v3) fail
--- Additional Comments From nickc at redhat dot com 2008-11-18 14:07
---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC:
could not read symbols: Bad value
Hi Rainer,
Unfortunately, regtesting the resulting GCC build is
currently hampered by the following
--- Additional Comments From ro at TechFak dot Uni-Bielefeld dot DE
2008-11-18 14:10 ---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC: could not
read symbols: Bad value
Hi Nick,
I think that this is a separate problem, rather than fallout from the
certainly.
Hi Rainer,
I'll try. First of all, I need to understand what the warning is all
about.
Oh, well the progbits attribute indicates that the section contains
data values, but the .bss section should in theory be completely empty
and just initialized with zero bytes when the program is loaded
--- Additional Comments From nickc at redhat dot com 2008-11-18 14:21
---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC:
could not read symbols: Bad value
Hi Rainer,
I'll try. First of all, I need to understand what the warning is all
about.
Oh, well
--- Additional Comments From ro at TechFak dot Uni-Bielefeld dot DE
2008-11-18 14:41 ---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC: could not
read symbols: Bad value
Hi Nick,
Oh, well the progbits attribute indicates that the section contains
data values,
Hi Rainer,
Every single one of the libstdc++ object files is affected. E.g.
% readelf -S --wide .libs/wstring-inst.o |grep -A1 '\.bss'
[191] .bss._ZZL18__gthread_active_pvE21__gthread_active_once PROGBITS
0205a8 20 00 WA 0 0 8
If I assemble the same
--- Additional Comments From nickc at redhat dot com 2008-11-18 15:11
---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC:
could not read symbols: Bad value
Hi Rainer,
Every single one of the libstdc++ object files is affected. E.g.
% readelf -S --wide
--- Additional Comments From ro at TechFak dot Uni-Bielefeld dot DE
2008-11-18 18:23 ---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC: could not
read symbols: Bad value
Hi Nick,
So, are you saying that assembling with gas v2.19 fixes the problem ?
indeed:
--- Additional Comments From nickc at redhat dot com 2008-11-17 16:46
---
Created an attachment (id=3065)
-- (http://sourceware.org/bugzilla/attachment.cgi?id=3065action=view)
Another patch attempt
--
What|Removed |Added
--- Additional Comments From nickc at redhat dot com 2008-11-17 16:47
---
Hi Rainer,
OK taking Ian's comments into account I have uploaded another attempt at a
patch for this problem. Please could you try it out and let me know if it is
any good ?
Cheers
Nick
--
--- Additional Comments From ro at TechFak dot Uni-Bielefeld dot DE
2008-11-17 17:29 ---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC: could not
read symbols: Bad value
Hi Nick,
OK taking Ian's comments into account I have uploaded another attempt at a
Hi Rainer,
unfortunately, ld SEGVs now here:
#0 0x0008d19c in _bfd_sparc_elf_check_relocs (abfd=0x1dc518, info=0x19d980,
sec=0x1f6a28, relocs=0x1fdc18) at
/vol/gnu/src/binutils/binutils-dist/bfd/elfxx-sparc.c:1348
Doh. Thinko in the patch. Please change:
case R_SPARC_WPLT30:
/*
--- Additional Comments From nickc at redhat dot com 2008-11-17 17:41
---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC:
could not read symbols: Bad value
Hi Rainer,
unfortunately, ld SEGVs now here:
#0 0x0008d19c in _bfd_sparc_elf_check_relocs
--- Additional Comments From ro at TechFak dot Uni-Bielefeld dot DE
2008-11-17 17:48 ---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC: could not
read symbols: Bad value
Hi Nick,
(Only the last line has changed).
done, but not much better either: at first I
--- Additional Comments From nickc at redhat dot com 2008-11-17 17:54
---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC:
could not read symbols: Bad value
Hi Rainer,
done, but not much better either: at first I get a lot of assertion
failures
Ok, this is
--- Additional Comments From ro at TechFak dot Uni-Bielefeld dot DE
2008-11-17 18:02 ---
Created an attachment (id=3068)
-- (http://sourceware.org/bugzilla/attachment.cgi?id=3068action=view)
problematic object file
--
http://sourceware.org/bugzilla/show_bug.cgi?id=7027
---
--- Additional Comments From ro at TechFak dot Uni-Bielefeld dot DE
2008-11-17 18:13 ---
Created an attachment (id=3069)
-- (http://sourceware.org/bugzilla/attachment.cgi?id=3069action=view)
object file that shows both the original and new problems
--
What|Removed
--- Additional Comments From ro at TechFak dot Uni-Bielefeld dot DE
2008-11-17 18:13 ---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC: could not
read symbols: Bad value
Hi Nick,
Ok, this is going nowhere. Is it possible for you to create a small
testcase
--- Additional Comments From ian at airs dot com 2008-11-16 18:33 ---
I didn't write the code in question. The code I added was simple: if there is a
R_SPARC_WPLT30 reloc against a symbol for which no PLT entry was created, we
handle it as a R_SPARC_WDISP30 reloc. That is
--- Additional Comments From nickc at redhat dot com 2008-11-14 09:18
---
Created an attachment (id=3062)
-- (http://sourceware.org/bugzilla/attachment.cgi?id=3062action=view)
Guess at how to handle local WPLT30 relocations for 64-bit sparc.
--
--- Additional Comments From nickc at redhat dot com 2008-11-14 09:19
---
Hi Rainer,
I am not familiar with the Sparc architecture, but I have uploaded a possible
patch which might fix the problem you discovered. Please could you try it out
and let me know if it really works ?
--- Additional Comments From ro at TechFak dot Uni-Bielefeld dot DE
2008-11-14 14:15 ---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC: could not
read symbols: Bad value
Hi Nick,
I am not familiar with the Sparc architecture, but I have uploaded a
possible
Hi Rainer,
+ if ((! ABI_64_P (abfd) ELF32_R_TYPE (rel-r_info) ==
R_SPARC_PLT32)
+ || (ABI_64_P (abfd) ELF32_R_TYPE (rel-r_info) ==
R_SPARC_PLT64))
The ABI_64_P() part doesn't trigger since ELF32_R_TYPE (rel-r_info) is 18
(i.e. R_SPARC_WPLT30) at this point. I
--- Additional Comments From nickc at redhat dot com 2008-11-14 14:51
---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC:
could not read symbols: Bad value
Hi Rainer,
+ if ((! ABI_64_P (abfd) ELF32_R_TYPE (rel-r_info) ==
R_SPARC_PLT32)
+
--- Additional Comments From ro at TechFak dot Uni-Bielefeld dot DE
2008-11-14 15:09 ---
Subject: Re: 64-bit libstdc++.so fails to link on Solaris 11/SPARC: could not
read symbols: Bad value
Hi Nick,
As a matter of interest if you change this to:
if ((! ABI_64_P (abfd)
29 matches
Mail list logo
