From: Jesus Antonio <jesusantonio30122016@gmail.com>
To: gcc@gcc.gnu.org
Subject: S390 should change the meaning of -m31
Date: Wed, 29 Sep 2021 18:41:19 -0500 [thread overview]
Message-ID: <e12c3433-7b62-b99c-5b13-0c696ab42c8b@gmail.com> (raw)
m31 is semantically the same as the m32 option.
The m31 option allows for 32 bit addressing and that is confusing since
the m31 option in S390 would mean 2 GiB space addressing but it allows
for 32 bit addressing, this is awkward, not only because the option is
misleading but is also incorrect.
To use 32 bit mode you specify m31, however in S390 there are 32 and 31
bit modes, which have only 1 bit in difference.
Code used:
volatile uint64_t *gib_test = (volatile uint64_t *)0x7FFFFFFF;
memset(gib_test, 1, 4096);
Hercules dump:
r 0x7FFFFFFF-0x800001FF
R:000000007FFFFFFF:K:06=01 .
R:000000008000000F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000001F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000002F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000003F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000004F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000005F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000006F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000007F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000008F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000009F:K:06=01 01010101 01010101 01010101 010101
................
R:00000000800000AF:K:06=01 01010101 01010101 01010101 010101
................
R:00000000800000BF:K:06=01 01010101 01010101 01010101 010101
................
R:00000000800000CF:K:06=01 01010101 01010101 01010101 010101
................
R:00000000800000DF:K:06=01 01010101 01010101 01010101 010101
................
R:00000000800000EF:K:06=01 01010101 01010101 01010101 010101
................
R:00000000800000FF:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000010F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000011F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000012F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000013F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000014F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000015F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000016F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000017F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000018F:K:06=01 01010101 01010101 01010101 010101
................
R:000000008000019F:K:06=01 01010101 01010101 01010101 010101
................
R:00000000800001AF:K:06=01 01010101 01010101 01010101 010101
................
R:00000000800001BF:K:06=01 01010101 01010101 01010101 010101
................
R:00000000800001CF:K:06=01 01010101 01010101 01010101 010101
................
R:00000000800001DF:K:06=01 01010101 01010101 01010101 010101
................
R:00000000800001EF:K:06=01 01010101 01010101 01010101 010101
................
R:00000000800001FF:K:06=01 01010101 01010101 01010101 010101
................
The option i used was m31 of course, however this option is misleading
since it allows 32 bit mode, and there is no m32 so you have to use m31
- just lots of misleading options.
I'm requesting that m31 and m32 are semantically different to allow a
less-misleading naming, since there is no 31 bit restriction whatsoever.
next reply other threads:[~2021-09-29 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 23:41 Jesus Antonio [this message]
2021-09-30 16:05 ` Michael Matz
2021-09-30 22:01 Paul Edwards
2021-10-08 8:02 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=e12c3433-7b62-b99c-5b13-0c696ab42c8b@gmail.com \
--to=jesusantonio30122016@gmail.com \
--cc=gcc@gcc.gnu.org \
/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).