Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@redhat.com>
To: Thomas Koeller <thomas.koeller@baslerweb.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Fix gcc-3.4.x compilation
Date: Tue, 27 Jul 2004 10:46:20 +0100	[thread overview]
Message-ID: <87fz7dvl3n.fsf@redhat.com> (raw)
In-Reply-To: <200407261237.09965.thomas.koeller@baslerweb.com> (Thomas Koeller's message of "Mon, 26 Jul 2004 12:37:09 +0200")

Thomas Koeller <thomas.koeller@baslerweb.com> writes:
> Since the meaning of 'accum' used to be 'hi' and 'lo', all its uses
> were clearly redundant.

For the record, that isn't quite true.  GCC internally treated
"accum" as an entirely separate register (which is why it became
such a headache).  In theory, if you have an instruction that
clobbers lo and hi, but doesn't clobber "accum", gcc might think
that a value in "accum" will still be valid.

Richard

      reply	other threads:[~2004-07-27  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26 10:37 [PATCH] Fix gcc-3.4.x compilation Thomas Koeller
2004-07-27  9:46 ` Richard Sandiford [this message]

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=87fz7dvl3n.fsf@redhat.com \
    --to=rsandifo@redhat.com \
    --cc=linux-mips@linux-mips.org \
    --cc=thomas.koeller@baslerweb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox