All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Rumpf <prumpf@puffin.external.hp.com>
To: Alan Modra <alan@linuxcare.com.au>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] New binutils available from cvs
Date: Thu, 18 May 2000 03:45:36 -0600	[thread overview]
Message-ID: <20000518034536.A14031@puffin.external.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0005181154270.24452-100000@front.linuxcare.com.au>; from Alan Modra on Thu, May 18, 2000 at 12:41:13PM +1000

On Thu, May 18, 2000 at 12:41:13PM +1000, Alan Modra wrote:
> Hello everyone,
>    I have just uploaded a new binutils to puffin.external.hp.com cvs.  The
> new binutils, which you can get with "cvs co binutils-2.10", is a merge of

Any reason for renaming cvs modules all the time instead of staying with
one name and perhaps not pissing off people with slow, expensive
connections ?

> ***BIG WARNING**
>   This binutils goes back to using the standard hppa comment char and line
> separator char.  Existing puffin parisc code needs to be modified to suit,

This
 a) makes certain glbic code harder to work (which already does work, at
    that)
 b) is inconsistent with every single other architecture that does run
    Linux
 c) is inconsistent with my tree, and basically forces me to distribute
    binutils and gcc patches in addition to the gcc one-liner I already
    have.

All in all this strikes me as not too smart.

BTW, did you fix gcc to work with -mdisable-fpregs and actually make the
kernel use that in the CVS tree ?  It caused a lot of oopses here before
I worked around it (patch is at
ftp://linux-parisc.sourceforge.net/pub/linux-parisc/) (why we got oopses
and what is wrong should be quite obvious if you know RTL - I don't and
it seems reasonably obvious to me, I just can't fix it).

	Philipp Rumpf

  reply	other threads:[~2000-05-18 10:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-18  2:41 [parisc-linux] New binutils available from cvs Alan Modra
2000-05-18  9:45 ` Philipp Rumpf [this message]
2000-05-18 10:37   ` Alan Modra
2000-05-18 10:51     ` Philipp Rumpf
2000-05-18 11:09       ` Alan Modra
2000-05-18 12:48         ` Philipp Rumpf
2000-05-18 13:19           ` Alan Modra
2000-05-18 15:23         ` Jeffrey A Law
2000-05-18 16:19       ` Grant Grundler
     [not found] <alan@linuxcare.com.au>
2000-05-18 17:26 ` Tor Arntsen
2000-05-18 19:40   ` willy

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=20000518034536.A14031@puffin.external.hp.com \
    --to=prumpf@puffin.external.hp.com \
    --cc=alan@linuxcare.com.au \
    --cc=parisc-linux@thepuffingroup.com \
    /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.