From: Andreas Jaeger <aj@suse.de>
To: "Martin Schwidefsky" <schwidefsky@de.ibm.com>
Cc: binutils@sourceware.cygnus.com
Subject: Re: New branch instructions for s/390.
Date: Wed, 22 Aug 2001 23:39:00 -0000 [thread overview]
Message-ID: <hog0aj8elb.fsf@gee.suse.de> (raw)
In-Reply-To: <OF9E1D2CD9.F37D952F-ONC1256AAE.0030C907@de.ibm.com>
"Martin Schwidefsky" <schwidefsky@de.ibm.com> writes:
> Hi,
> gcc 3.0 wants to have branch instructions for "low or high" and
> "not low or high". Here is a patch that adds them to the s/390
> instruction list.
>
> 2001-08-20 Martin Schwidefsky <schwidefsky@de.ibm.com>
>
> * opcodes/s390-opc.c: Add "low or high" and "not low or high"
> branch instructions for gcc 3.0.
> * opcodes/s390-opc.txt: Likewise.
>
> (See attached file: lh_nlh.diff)
I've added this to CVS since you're the maintainer and don't have CVS
access.
Thanks,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2001-08-22 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-20 2:01 Martin Schwidefsky
2001-08-22 23:39 ` Andreas Jaeger [this message]
2001-08-23 11:19 Martin Schwidefsky
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=hog0aj8elb.fsf@gee.suse.de \
--to=aj@suse.de \
--cc=binutils@sourceware.cygnus.com \
--cc=schwidefsky@de.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).