public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: GOTO Masanori <gotom@debian.or.jp>
To: Richard Henderson <rth@twiddle.net>
Cc: libc-alpha@sources.redhat.com, gcc@gcc.gnu.org,
	debian-glibc@lists.debian.org
Subject: Re: [rfc] alpha-linux changing to 128-bit long double
Date: Mon, 08 Mar 2004 01:28:00 -0000	[thread overview]
Message-ID: <81y8qcyvn1.wl@omega.webmasters.gr.jp> (raw)
In-Reply-To: <20040307055826.GA1244@twiddle.net>

At Sat, 6 Mar 2004 21:58:26 -0800,
Richard Henderson wrote:
> I would be comfortable getting all this done for glibc 2.3.4, and
> just say "use an older release if you don't want this abi change."
> Seems to me the ifdeffery (and worse, makefile ifdeffery) would be
> too awful to considering supporting both modes simultaneously.
> 
> As for gcc, I suppose I'll have to do something like a different
> configuration name, such as alpha-dec-linux-glibc6.2?  The patches
> to gcc (for any recent version) should be small; the support is
> already present because of Tru64, just have to turn it on.
> 
> Cc'ed to debian-glibc, since they're the only currently viable alpha
> distribution that I'm aware of.  I see yall are still using glibc
> 2.3.2.  What are debian's plans here wrt the next release (if there's
> ever to be one)?

We're no problem of the transition to libc6.2, and we can help you
(ex) build and test various packages using newer libc on alpha.

Unfortunatelly, Debian/sarge (next release) is getting to the final
step, so it's hard to replace libc6.1.  I'm impatient for debian's
current glibc to update its version which is based on the last year
(September) cvs, but it's still time to wait for new release.  So this
transition will be after sarge.

Regards,
-- gotom

  parent reply	other threads:[~2004-03-08  1:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-07  5:58 Richard Henderson
2004-03-07 22:34 ` Ulrich Drepper
2004-03-08  1:28 ` GOTO Masanori [this message]
2004-03-09 18:38 ` Falk Hueffner
2004-03-13 10:17 ` Jakub Jelinek
2004-03-14  1:58   ` Richard Henderson
2004-03-13 16:36 Ulrich Weigand

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=81y8qcyvn1.wl@omega.webmasters.gr.jp \
    --to=gotom@debian.or.jp \
    --cc=debian-glibc@lists.debian.org \
    --cc=gcc@gcc.gnu.org \
    --cc=libc-alpha@sources.redhat.com \
    --cc=rth@twiddle.net \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).