Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] More from the TLS glibc front.
Date: Sun, 10 Apr 2005 03:44:03 -0700	[thread overview]
Message-ID: <20050410104403.GK6987@tausq.org> (raw)
In-Reply-To: <20050409050558.GL1833@baldric.uwo.ca>

> 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

       reply	other threads:[~2005-04-10 10:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050409050558.GL1833@baldric.uwo.ca>
2005-04-10 10:44 ` Randolph Chung [this message]
2005-04-15 14:33   ` [parisc-linux] More from the TLS glibc front Carlos O'Donell
2005-04-15 14:34   ` Carlos O'Donell
2005-04-15 16:30   ` Carlos O'Donell
     [not found] <4257AE83.6030308@tiscali.be>
2005-04-09 15:15 ` John David Anglin
2005-04-09 16:57   ` Joel Soete
2005-04-09 17:19     ` John David Anglin
2005-04-15 14:30       ` Carlos O'Donell
2005-04-15 16:05         ` John David Anglin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050410104403.GK6987@tausq.org \
    --to=randolph@tausq.org \
    --cc=carlos@baldric.uwo.ca \
    --cc=parisc-linux@lists.parisc-linux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox