From: Joel Soete <soete.joel@tiscali.be>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] More from the TLS glibc front.
Date: Sat, 09 Apr 2005 16:57:18 +0000 [thread overview]
Message-ID: <4258096E.1050205@tiscali.be> (raw)
In-Reply-To: <200504091515.j39FFtij022153@hiauly1.hia.nrc.ca>
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
next prev parent reply other threads:[~2005-04-09 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4257AE83.6030308@tiscali.be>
2005-04-09 15:15 ` [parisc-linux] More from the TLS glibc front John David Anglin
2005-04-09 16:57 ` Joel Soete [this message]
2005-04-09 17:19 ` John David Anglin
2005-04-15 14:30 ` Carlos O'Donell
2005-04-15 16:05 ` John David Anglin
[not found] <20050409050558.GL1833@baldric.uwo.ca>
2005-04-10 10:44 ` Randolph Chung
2005-04-15 14:33 ` Carlos O'Donell
2005-04-15 14:34 ` Carlos O'Donell
2005-04-15 16:30 ` Carlos O'Donell
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=4258096E.1050205@tiscali.be \
--to=soete.joel@tiscali.be \
--cc=dave@hiauly1.hia.nrc.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