From: Andreas Jaeger <aj@suse.de>
To: "H . J . Lu" <hjl@lucon.org>
Cc: linux-mips@oss.sgi.com, GNU C Library <libc-alpha@sources.redhat.com>
Subject: Re: PATCH: Not use branch likely on mips
Date: Fri, 08 Feb 2002 09:00:02 +0100 [thread overview]
Message-ID: <hou1sswghp.fsf@gee.suse.de> (raw)
In-Reply-To: <20020207091327.B15331@lucon.org> ("H . J . Lu"'s message of "Thu, 7 Feb 2002 09:13:27 -0800")
"H . J . Lu" <hjl@lucon.org> writes:
> On Thu, Feb 07, 2002 at 11:38:09AM +0100, Andreas Jaeger wrote:
>> "H . J . Lu" <hjl@lucon.org> writes:
>>
>> > This patch removes branch likely.
>>
>> Please update the copyright years next time.
>>
>> I've committed the patch,
>>
>
> Here is a new patch. I have checked in a gcc patch which makes
> ".set noreorder" unnecessary even with "gcc -g".
But what about current GCC releases? Does it work there also without
problems?
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2002-02-08 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 2:02 PATCH: Not use branch likely on mips H . J . Lu
2002-02-07 10:38 ` Andreas Jaeger
2002-02-07 17:13 ` H . J . Lu
2002-02-08 8:00 ` Andreas Jaeger [this message]
2002-02-08 12:03 ` Maciej W. Rozycki
2002-02-08 16:15 ` Andreas Jaeger
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=hou1sswghp.fsf@gee.suse.de \
--to=aj@suse.de \
--cc=hjl@lucon.org \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-mips@oss.sgi.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