Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] FYI: state of toolchain for Debian woody release
Date: Sat, 9 Mar 2002 10:35:24 -0800	[thread overview]
Message-ID: <20020309183524.GC628@tausq.org> (raw)

Just thought I'd post a quick note about some of the things happening
recently:

With many thanks to Dave Anglin and the investigation work by Carlos
O'Donell, we've finally fixed the bug in gcc-3.0 that affected passing
floating point arguments in indirect calls.

The new compilers are now in the Debian archive, and we are slowly
starting to rebuild some of the affected packages. (gs and python2.1
were the ones I knew about offhand, and they are now in the incoming
queue). If you know of any other Debian packages you use that might be
affected by this bug, let us know and we'll rebuild it.

There are still some known problems with the compilers, most notably the
problems with fixups that aren't able to reach their targets and thus 
requiring compilation with -ffunction-section. I have one patch from
Dave that fixes this in some cases, but as I understand it the general
problem is more involved and might not get fixed till post-woody.

gdb also seems to be rather broken on hppa at the moment. Single
stepping doesn't always (doesn't usually) work, and there's a problem 
with recognizing core files. If anyone has time to look into these 
and submit patches, that'll be great!

randolph
-- 
   @..@                                         http://www.TauSq.org/
  (----)
 ( >__< )
 ^^ ~~ ^^

             reply	other threads:[~2002-03-09 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-09 18:35 Randolph Chung [this message]
2002-03-09 18:56 ` [parisc-linux] FYI: state of toolchain for Debian woody release 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=20020309183524.GC628@tausq.org \
    --to=randolph@tausq.org \
    --cc=parisc-linux@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