Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <tausq@debian.org>
To: Matthias Klose <doko@cs.tu-berlin.de>
Cc: parisc-linux@lists.parisc-linux.org,
	debian-hppa@lists.debian.org, debian-gcc@lists.debian.org
Subject: [parisc-linux] Re: gcc-3.? compiler for hppa (3.1, 3.1+dwarf2, 3.2cvs20020429?)
Date: Sat, 4 May 2002 09:57:40 -0700	[thread overview]
Message-ID: <20020504165740.GN30370@tausq.org> (raw)
In-Reply-To: <15571.50195.280071.792305@gargle.gargle.HOWL>

> a) 3.1 as to be released (without dwarf2 support)
> b) 3.1 + dwarf2 support
> c) 3.2 CVS 20020429 plus/minus patches

for woody+1, is it an option to skip 3.1 altogether and go directly to
3.2? from what i understand gcc-3.2 is supposed to be officially 
released in the fall...  (i.e. likely before the next release)

i am concerned that between gcc versions, there are often changes in the
C++ (and maybe others) ABI, and moving all of our packages to the new 
version is likely going to be a painful process. If the g++-3.2 ABI is
already frozen (?) and we move directly to it then we may save ourselves
some trouble with doing the repackaging multiple times.

of course there is also the concern that we want to remain at least
somewhat binary compatible with other distributions...

IMHO, for hppa I think a pure option (a) is not feasible for woody+1. 
The long branch problem by itself is something that I feel needs to 
be addressed as soon as possible. Also I'm eager to have working
exceptions support for c++ :-)

Oh, by the way, when we move woody to gcc-3.[12] as the default, will we
still have gcc-3.0 packages available?

randolph

  reply	other threads:[~2002-05-04 16:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-04 11:20 [parisc-linux] gcc-3.? compiler for hppa (3.1, 3.1+dwarf2, 3.2cvs20020429?) Matthias Klose
2002-05-04 16:57 ` Randolph Chung [this message]
2002-05-04 17:54   ` [parisc-linux] " John David Anglin
2002-05-04 17:54   ` John David Anglin
2002-05-06 14:32     ` Phil Edwards
2002-05-06 14:32     ` Phil Edwards
2002-05-08 21:50       ` John David Anglin
2002-05-08 21:50       ` John David Anglin
2002-05-04 16:57 ` Randolph Chung
2002-05-04 17:47 ` [parisc-linux] " John David Anglin
2002-05-04 17:47 ` John David Anglin
2002-05-05 12:41   ` Matthias Klose
2002-05-05 15:45     ` John David Anglin
2002-05-05 16:35       ` Matthias Klose
2002-05-05 16:35       ` Matthias Klose
2002-05-05 15:45     ` John David Anglin
2002-05-05 22:32     ` Grant Grundler
2002-05-05 22:32     ` Grant Grundler
2002-05-05 12:41   ` Matthias Klose
2002-05-05  6:54 ` [parisc-linux] " Martin v. Loewis
2002-05-05  6:56   ` Daniel Jacobowitz
2002-05-05  6:56   ` Daniel Jacobowitz
2002-05-05 12:30     ` Matthias Klose
2002-05-05 12:30     ` Matthias Klose
2002-05-05  6:54 ` Martin v. Loewis

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=20020504165740.GN30370@tausq.org \
    --to=tausq@debian.org \
    --cc=debian-gcc@lists.debian.org \
    --cc=debian-hppa@lists.debian.org \
    --cc=doko@cs.tu-berlin.de \
    --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