Re: [parisc-linux] More from the TLS glibc front.

Re: [parisc-linux] More from the TLS glibc front.

[Randolph Chung]

> Still tacking:

Hmm.... I guess I must be using slightly different sources, and I see
different problems....

I'm using:
binutils CVS HEAD (20050409)
gcc-4.0-20050402 (ftp'ed)
glibc CVS HEAD (20050409)

First of all, the patches seem to be out of date. I've updated the
binutils and gcc ones.

http://www.parisc-linux.org/~tausq/hppa-tls-gcc.diff
http://www.parisc-linux.org/~tausq/hppa-tls-binutils.diff

I find some other issues with the glibc build. Carlos, a few of your
patches are malformed. They have CVS conflict markers in them.. :)

Right now my build fails when building tst-tlsmod14a.c with a gcc ICE. I
think my gcc patches are broken (no surprise there...)

I'll try to take a closer look at the gcc failure. The failure looks
like this (simplified to a small test program):

$ /home/tausq/tls/bin/gcc -O2 -fPIC -c tlstst.c
tlstst.c: In function 'in_dso1':
tlstst.c:21: error: unable to find a register to spill in class 'R1_REGS'
tlstst.c:21: error: this is the insn:
(insn 26 20 23 0 (set (reg:SI 28 %r28 [106])
        (plus:SI (reg:SI 19 %r19)
            (high:SI (symbol_ref/v/f:SI ("*.LC0") [flags 0x2] <string_cst 0x400b8780>)))) 46 {*pa.md:2717} (nil)
    (nil))
tlstst.c:21: confused by earlier errors, bailing out

Only happens with -fPIC. Likely I'm doing the rtl wrong in
legitimize_tls_address ()

tlstst.c is at http://www.parisc-linux.org/~tausq/tlstst.c

btw, Carlos, are you building glibc with linuxthreads or nptl when you
enable TLS? If I use nptl I get a lot of build errors very early in the
build process.

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

Re: [parisc-linux] More from the TLS glibc front.

[Carlos O'Donell]

On Sun, Apr 10, 2005 at 03:44:03AM -0700, Randolph Chung wrote:
> btw, Carlos, are you building glibc with linuxthreads or nptl when you
> enable TLS? If I use nptl I get a lot of build errors very early in the
> build process.

Disable nptl, we don't have the patches for that to work yet, since we
don't have a working futex prototype.

I am building with:

$SRC/$LIBC/configure --host=$ARCH-linux --build=$ARCH-linux
--target=$ARCH-linux --prefix=$GINSTALL --enable-add-ons=linuxthreads
--enable-tls --enable-__thread  --enable-all-warnings >&
../configure-$BUILDNAME-$ARCH.log

c.

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

Re: [parisc-linux] More from the TLS glibc front.

[Carlos O'Donell]

On Sun, Apr 10, 2005 at 03:44:03AM -0700, Randolph Chung wrote:
> I find some other issues with the glibc build. Carlos, a few of your
> patches are malformed. They have CVS conflict markers in them.. :)

Oh, yes. I'm not always as careful as I want to be with that patch
generation. I fix the upstream glibc problems too fast, and the update
script does a 'cvs up' and then generates patches. Not always optimal.

c.

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

Re: [parisc-linux] More from the TLS glibc front.

[Carlos O'Donell]

On Sun, Apr 10, 2005 at 03:44:03AM -0700, Randolph Chung wrote:
> I'm using:
> binutils CVS HEAD (20050409)
> gcc-4.0-20050402 (ftp'ed)
> glibc CVS HEAD (20050409)
> 
> First of all, the patches seem to be out of date. I've updated the
> binutils and gcc ones.
> 
> http://www.parisc-linux.org/~tausq/hppa-tls-gcc.diff
> http://www.parisc-linux.org/~tausq/hppa-tls-binutils.diff
> 
> I find some other issues with the glibc build. Carlos, a few of your
> patches are malformed. They have CVS conflict markers in them.. :)
> 
> Right now my build fails when building tst-tlsmod14a.c with a gcc ICE. I
> think my gcc patches are broken (no surprise there...)

Woah, wait a second. You have a working build? You got to atleast the
check phase if you are building the tests. Are you sure your build made
it all the way through?

How did you fix this:
/mnt/flaire/src/tls-toolchain/install/bin/../lib/gcc/hppa-linux/3.4.3/../../../../hppa-linux/bin/ld:
__libc_errno: TLS definition in
/home/carlos/fsrc/tls-toolchain/build/libc/2005-04-08-hppa/libc_pic.a(errno.os)
section .tbss mismatches non-TLS reference in
/home/carlos/fsrc/tls-toolchain/build/libc/2005-04-08-hppa/libc_pic.a(getcwd.os)


c.

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

Re: [parisc-linux] More from the TLS glibc front.

[John David Anglin]

> 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
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

Re: [parisc-linux] More from the TLS glibc front.

[Joel Soete]

John David Anglin wrote:
>>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?)

> 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
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

Re: [parisc-linux] More from the TLS glibc front.

[John David Anglin]

> > 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?)
> 
> > 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
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
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
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

Re: [parisc-linux] More from the TLS glibc front.

[Carlos O'Donell]

On Sat, Apr 09, 2005 at 01:19:35PM -0400, John David Anglin wrote:
> 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
> -- 
> J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
> 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)						\
>  {									\

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
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

Re: [parisc-linux] More from the TLS glibc front.

[John David Anglin]

> 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
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux