Skip to contentSkip to conversation

More from the TLS glibc front.

parisc-linux John David Anglin 3 participants 5 messages Apr 9, 2005 – Apr 15, 2005 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 4 lines

what's up with gcc-3.3.x?
I never reach to complet the glibc build with gcc-3.4 (see detailed investigation in
<http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17471>), gcc-3.5 at this time (now gcc-4) seems to solve this pb even thought there was some other pb to fix with this new compiler ;-S (but not enough time to investigate, sorry)

I'm not aware of any GCC PRs related to this. A few PA specific bug fixes have been back ported to 3.3 and 3.4.

Dave

Signature · 6 lines
J. David Anglin                                  [email protected]
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
#2 lore raw
Quoted 5 lines · John David Anglin
Quoted 2 lines

what's up with gcc-3.3.x?
I never reach to complet the glibc build with gcc-3.4 (see detailed investigation in <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17471>), gcc-3.5 at this time (now gcc-4) seems to solve this pb even thought there was some other pb to fix with this new compiler ;-S (but not enough time to investigate, sorry)

I'm not aware of any GCC PRs related to this.

Sorry iirc those new pb wouldn't have to be the object of gcc pr but would more need some small changes in the glibc code to take into account the new gcc-4.x (may be some more always_use arrtibute?)

Quoted 3 lines

A few PA specific bug fixes
have been back ported to 3.3 and 3.4.

well mentioned pr #17471 was 2.3.3 glibc and 3.4 gcc related; today 2.3.5 is out, if I find some more free time I will try this new 2.3.5 glibc with new 4.? gcc

Thanks for feedback,
Joel
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

#3 lore raw
Quoted 9 lines
Quoted 1 line

I'm not aware of any GCC PRs related to this.

Sorry iirc those new pb wouldn't have to be the object of gcc pr but would more need some small changes in the glibc code to take into account the new gcc-4.x (may be some more always_use arrtibute?)

Quoted 3 lines

A few PA specific bug fixes
have been back ported to 3.3 and 3.4.

well mentioned pr #17471 was 2.3.3 glibc and 3.4 gcc related; today 2.3.5 is out, if I find some more free time I will try this new 2.3.5 glibc with new 4.? gcc

Well, your analysis in 17471 didn't convince me that a gcc code generation bug was involved. I believe that if you try the change below that glibc will build with 3.3 and 3.4. There was a warning generated by GCC.

I thought this was fixed in glibc.

Dave

Signature · 17 lines
J. David Anglin                                  [email protected]
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

--- dl-machine.h.orig	2004-10-22 20:01:03.000000000 -0700
+++ dl-machine.h	2004-10-22 21:32:30.000000000 -0700
@@ -260,6 +260,7 @@
 
 #define RTLD_START \
 /* Set up dp for any non-PIC lib constructors that may be called.  */	\
+static struct link_map *set_dp (struct link_map *) __attribute__ ((used));\
 static struct link_map *						\
 set_dp (struct link_map *map)						\
 {									\
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
#4 lore raw
Quoted 14 lines · John David Anglin

Well, your analysis in 17471 didn't convince me that a gcc code generation bug was involved. I believe that if you try the change below that glibc will build with 3.3 and 3.4. There was a warning generated by GCC.

I thought this was fixed in glibc.

Dave

Signature · 2 lines
J. David Anglin                                  [email protected]
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

dl-machine.h line 266

Quoted 7 lines
dl-machine.h renamed from dl-machine.h.orig +1 -0
@@ -260,6 +260,7 @@
 
 #define RTLD_START \
 /* Set up dp for any non-PIC lib constructors that may be called.  */	\
+static struct link_map *set_dp (struct link_map *) __attribute__ ((used));\
 static struct link_map *						\
 set_dp (struct link_map *map)						\
 {									\

It *is* fixed, if you look at the patches I posted that is part of the diff against dl-machine.h.

Note: gcc 3.5 or higher is now required to build glibc.

c.

_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

#5 lore raw
Quoted 1 line

Note: gcc 3.5 or higher is now required to build glibc.

3.5 doesn't exist. This should be 4.0.0. However, I'm surprised that 3.3.5 or 3.4.3 don't work. They both have more test history.

Dave

Signature · 6 lines
J. David Anglin                                  [email protected]
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux