Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@tiscali.be>
To: Kyle McMartin <kyle@engsoc.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 	Heads up,	2.6.7-pa0 FTBS with 64-bit toolchain + loop
Date: Sat, 19 Jun 2004 22:59:10 +0000	[thread overview]
Message-ID: <40D4C53E.5000309@tiscali.be> (raw)
In-Reply-To: <20040619015455.GE12572@engsoc.org>

Hello all,

And there is also this pb mentionned by James:
<http://lists.parisc-linux.org/pipermail/parisc-linux/2004-February/022335.html>

regarding the pb of pointer comparison with gcc-3.3 and 3.4 64bits (sorry I didn't find back the gcc bug report reference) which 
iirc jda re-qualified it in a binutils pb. (That why of my interest in binutils 2.15 :) to see if I can help.)

That said, my very interest in 3.4 (and 3.5 now because is became the debian gcc-snapshot ;) ) is to continue the glibc-2.3.3 test 
and see if additional integer lib (hp one iirc) can help for the few test which still failled?

I was focused last month on my c110 ncr53c8xx bug; now I trust it is fixed, so jda if you think that I can be of better help else 
where I can always try to have a look ;). Please advise.

Joel




Kyle McMartin wrote:
> On Fri, Jun 18, 2004 at 07:17:14PM -0600, Grant Grundler wrote:
> 
>>Should I be testing 64-bit kernels built with this toolchain
>>or stick with my trusty gcc 3.0.4-hppa64 handmade debs?
>>
> 
> There's a bug in hppa64 gcc sometime after 3.0.4 (it shows up in the
> gcc-3.3-hppa64 and gcc-3.4-hppa64 debs) that causes builds to fail in
> (at least) loop.c.
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14782 is the bug Randolph
> filed.
> 
> I've been building hppa64 kernels with the gcc 3.0.4 debs on the FTP
> server, until this issue is resolved. :/
> 
> Regards,

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

  parent reply	other threads:[~2004-06-19 22:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 19:44 [parisc-linux] Heads up, 2.6.7-pa0 FTBS with 64-bit toolchain + loop Carlos O'Donell
2004-06-18  0:22 ` Kyle McMartin
     [not found] ` <40D35B15.3040505@tiscali.be>
     [not found]   ` <20040618212505.GA12572@engsoc.org>
     [not found]     ` <20040619011714.GC23535@colo.lackof.org>
2004-06-19  1:35       ` [parisc-linux] Heads up, John David Anglin
     [not found]       ` <20040619015455.GE12572@engsoc.org>
2004-06-19  2:20         ` John David Anglin
2004-06-19 22:59         ` Joel Soete [this message]
2004-06-20  0:29           ` [parisc-linux] Heads up, 2.6.7-pa0 FTBS with 64-bit toolchain John David Anglin
2004-06-20  1:14             ` John David Anglin
2004-06-20 10:24               ` Matthias Klose
2004-06-21 16:36               ` Carlos O'Donell
2004-06-21 17:27               ` Kyle McMartin
2004-06-20  9:26           ` [parisc-linux] Heads up, 2.6.7-pa0 FTBS with 64-bit toolchain + loop Matthias Klose
     [not found]             ` <40D5B081.30508@tiscali.be>
2004-06-20 19:21               ` Matthias Klose

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=40D4C53E.5000309@tiscali.be \
    --to=soete.joel@tiscali.be \
    --cc=kyle@engsoc.org \
    --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