From: Ralf Baechle <ralf@linux-mips.org>
To: Long Li <long21st@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Possible bug in gcc for mips?
Date: Wed, 29 Jan 2003 08:12:56 +0100 [thread overview]
Message-ID: <20030129081256.B7741@linux-mips.org> (raw)
In-Reply-To: <20030129031421.89385.qmail@web40408.mail.yahoo.com>; from long21st@yahoo.com on Tue, Jan 28, 2003 at 07:14:21PM -0800
On Tue, Jan 28, 2003 at 07:14:21PM -0800, Long Li wrote:
> Subject: Possible bug in gcc for mips?
It's always possible to blame the tools for broken source.
> asm volatile ("mfc0 %0,$12" :: "r"(status_reg));
Make that:
asm volatile ("mfc0 %0,$12" : "=r"(status_reg));
> Is this a possible bug or a feature for gcc 3.0.4?
Yes. Broken source in, broken code out :-)
Ralf
prev parent reply other threads:[~2003-01-29 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 3:14 Possible bug in gcc for mips? Long Li
2003-01-29 7:12 ` Ralf Baechle [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=20030129081256.B7741@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=long21st@yahoo.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.