All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: carlos@baldric.uwo.ca (Carlos O'Donell)
Cc: parisc-linux@lists.parisc-linux.org, debian-hppa@lists.debian.org
Subject: Re: [parisc-linux] [Status] hppa's userspace in 2004 (looking back)
Date: Mon, 5 Jan 2004 13:48:54 -0500 (EST)	[thread overview]
Message-ID: <200401051848.i05Imt6p005065__28884.7856027589$1416623105$gmane$org@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <20040105172146.GE23782@systemhalted> from "Carlos O'Donell" at Jan 5, 2004 12:21:46 pm

> ======
> GNU/cc
> ======
> 
> jda, you're the best person to talk about how gcc is doing. I can build
> kernels with 3.3.3, sadly with the anon cvs down it's messed up my usual
> workflow when it comes to testing.

The PA backend is in fairly reasonable shape.  Most of the remaining
PA bugs are limitations in the current implementation.  We are still
restricted in distance for floating point and branch on bit.  Frame
sizes on hppa64 are limited to < 2**36 bytes.  There is a bug which
causes arguments in const functions to get optimized away.  There is
a bug which affects constant elimination.  On the 64-bit port, constants
don't appear to be substituted/combined properly with if_then_else
insns.  As a result, some if statements don't get simplified.

2004 Projects:

1) Squash remaining bugs and limitations.
2) Finish libffi port.
3) Add PA specific stuff for java.
4) Develop TLS specification and GCC support.
5) Allow small range of floating point registers to be used
   for integer multiplication in kernel.  This should help
   64-bit kernel.
6) Thread support for ada.

As usual, I expect there will be many ups and downs in the process.
So, we won't get as far as we would like.

> jda, you mentioned that the libstdc++ testsuite could be examined in
> order to fix some of our failures.

Yes, these need to be looked at before 3.4 is released.  Some appear
to be related to long double support.  Just guessing, but I think the
rest are locale or glibc related.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

  parent reply	other threads:[~2004-01-05 18:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 17:21 [parisc-linux] [Status] hppa's userspace in 2004 (looking back) Carlos O'Donell
2004-01-05 18:48 ` John David Anglin
2004-01-06  5:39   ` Carlos O'Donell
2004-01-06  5:39   ` Carlos O'Donell
2004-01-06  6:16     ` John David Anglin
2004-01-06 15:48       ` Carlos O'Donell
2004-01-06 15:48       ` Carlos O'Donell
2004-01-06  6:16     ` John David Anglin
2004-01-05 18:48 ` John David Anglin [this message]
2004-01-05 19:33 ` [parisc-linux] " Matthew Wilcox
2004-01-05 19:33 ` Matthew Wilcox
2004-01-05 21:45   ` Helge Deller
2004-01-05 21:45   ` Helge Deller
2004-01-06  0:00     ` Christopher Strong
2004-01-06  5:32       ` Carlos O'Donell
2004-01-08  8:06 ` [parisc-linux] " Joel Soete
2004-01-08  8:06 ` Joel Soete
2004-01-09 20:37   ` Joel Soete
2004-01-09 20:37   ` Joel Soete
2004-01-12 17:51     ` Joel Soete
2004-01-12 17:51     ` Joel Soete
  -- strict thread matches above, loose matches on Subject: below --
2004-01-05 17:21 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='200401051848.i05Imt6p005065__28884.7856027589$1416623105$gmane$org@hiauly1.hia.nrc.ca' \
    --to=dave@hiauly1.hia.nrc.ca \
    --cc=carlos@baldric.uwo.ca \
    --cc=debian-hppa@lists.debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.