From: Joe Monk <joemonk64@gmail.com>
To: Paul Edwards <mutazilah@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: s390 port
Date: Tue, 7 Sep 2021 02:21:21 -0500 [thread overview]
Message-ID: <CAPcd4G9crfy31zdT7rey3Oc6EFUAJvJa7ZtrNqazpt0cvZK=9Q@mail.gmail.com> (raw)
In-Reply-To: <BYAPR01MB54642CF4A5E02400CCBE04B1C6D09@BYAPR01MB5464.prod.exchangelabs.com>
It is unclear how this would even work.
For instance, the LA instruction clears the top bit.
Also, instructions like LPR, LNR, BXLE, BXH all treat the value in the
register as signed, so the top bit is not available.
Joe
next prev parent reply other threads:[~2021-09-07 7:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 22:44 Build gcc question Gary Oblock
2021-09-07 7:21 ` Joe Monk [this message]
2021-09-08 3:46 ` s390 port Paul Edwards
-- strict thread matches above, loose matches on Subject: below --
2023-01-28 18:51 Paul Edwards
2023-01-29 13:08 ` Joe Monk
2023-01-29 14:30 ` Paul Edwards
2021-09-30 21:39 Paul Edwards
2021-09-30 0:08 Paul Edwards
2021-09-30 0:59 ` Joe Monk
2021-09-02 10:56 Paul Edwards
2009-06-05 15:21 i370 port Ulrich Weigand
2021-09-02 8:15 ` s390 port Paul Edwards
2021-09-02 14:34 ` Ulrich Weigand
2021-09-02 14:50 ` Paul Edwards
2021-09-02 14:53 ` Ulrich Weigand
2021-09-02 15:01 ` Paul Edwards
2021-09-02 15:13 ` Ulrich Weigand
2021-09-02 15:26 ` Paul Edwards
2021-09-02 19:46 ` Ulrich Weigand
2021-09-02 20:05 ` Paul Edwards
2021-09-02 20:16 ` Andreas Schwab
2021-09-03 11:18 ` Ulrich Weigand
2021-09-03 11:35 ` Paul Edwards
2021-09-03 12:12 ` Ulrich Weigand
2021-09-03 12:38 ` Paul Edwards
2021-09-03 12:53 ` Jakub Jelinek
2021-09-03 13:12 ` Paul Edwards
2022-12-20 4:27 ` Paul Edwards
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='CAPcd4G9crfy31zdT7rey3Oc6EFUAJvJa7ZtrNqazpt0cvZK=9Q@mail.gmail.com' \
--to=joemonk64@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=mutazilah@gmail.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).