From: Andreas Schwab <schwab@suse.de>
To: David Brown <david.brown@hesbynett.no>
Cc: Martin Uecker <uecker@tugraz.at>, gcc@gcc.gnu.org
Subject: Re: aliasing
Date: Mon, 18 Mar 2024 14:54:12 +0100 [thread overview]
Message-ID: <mvma5mvk5mj.fsf@suse.de> (raw)
In-Reply-To: <6bff9afd-3e84-4260-9d05-8faec5f3ebe2@hesbynett.no> (David Brown's message of "Mon, 18 Mar 2024 14:29:15 +0100")
On Mär 18 2024, David Brown wrote:
> I think it would be possible to have an implementation where "signed
> char" was 8-bit two's complement except that 0x80 would be a trap
> representation rather than -128.
signed char cannot have padding bits, thus it cannot have a trap
representation.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2024-03-18 13:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 7:03 aliasing Martin Uecker
2024-03-18 8:26 ` aliasing Richard Biener
2024-03-18 10:55 ` aliasing Martin Uecker
2024-03-18 11:56 ` aliasing Martin Uecker
2024-03-18 13:21 ` aliasing Richard Biener
2024-03-18 15:13 ` aliasing Martin Uecker
2024-03-18 9:00 ` aliasing David Brown
2024-03-18 10:09 ` aliasing Jonathan Wakely
2024-03-18 11:41 ` aliasing Martin Uecker
2024-03-18 13:29 ` aliasing David Brown
2024-03-18 13:54 ` Andreas Schwab [this message]
2024-03-18 16:46 ` aliasing David Brown
2024-03-18 16:55 ` aliasing David Brown
2024-03-18 15:00 ` aliasing Martin Uecker
2024-03-18 17:11 ` aliasing David Brown
-- strict thread matches above, loose matches on Subject: below --
1999-08-21 9:23 aliasing Jason Moxham
1999-08-21 9:46 ` aliasing Mark Mitchell
1999-08-31 23:20 ` aliasing Mark Mitchell
1999-08-31 23:20 ` aliasing Jason Moxham
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=mvma5mvk5mj.fsf@suse.de \
--to=schwab@suse.de \
--cc=david.brown@hesbynett.no \
--cc=gcc@gcc.gnu.org \
--cc=uecker@tugraz.at \
/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).