From: Andreas Schwab <schwab@linux-m68k.org>
To: Zack Weinberg via Libc-alpha <libc-alpha@sourceware.org>
Cc: Carlos O'Donell <carlos@redhat.com>, Zack Weinberg <zack@owlfolio.org>
Subject: Re: “Undefined behavior” considered harmful (was Re: Bug 29863 - Segmentation fault in memcmp-sse2.S…)
Date: Thu, 29 Dec 2022 23:20:15 +0100 [thread overview]
Message-ID: <87y1qp97j4.fsf@igel.home> (raw)
In-Reply-To: <ypikr0wigg4d.wl-zack@owlfolio.org> (Zack Weinberg via Libc-alpha's message of "Thu, 29 Dec 2022 14:32:50 -0500")
On Dez 29 2022, Zack Weinberg via Libc-alpha wrote:
> 1. The C standard uses “undefined behavior” far more liberally than it
> ought to. In many cases of existing UB the committee could define
> the behavior (possibly as implementation-defined or unspecified)
> without any actual negative consequences. It seems the committee
> *is* moving in this direction as of C2x, for instance by dropping
> the allowances for non-twos-complement signed arithmetic, but they
> could and should go a lot farther down that road.
That's not removing an undefined behavior, it's removing an
implementation choice.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-12-29 22:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 18:20 Bug 29863 - Segmentation fault in memcmp-sse2.S if memory contents can concurrently change Narayanan Iyer
2022-12-13 18:31 ` Andrew Pinski
2022-12-13 18:39 ` Narayanan Iyer
2022-12-13 18:39 ` Cristian Rodríguez
2022-12-13 19:08 ` Noah Goldstein
2022-12-13 19:13 ` Narayanan Iyer
2022-12-13 19:25 ` Noah Goldstein
2022-12-13 20:56 ` Zack Weinberg
2022-12-13 23:29 ` Carlos O'Donell
2022-12-14 2:28 ` Zack Weinberg
2022-12-14 4:16 ` Carlos O'Donell
2022-12-14 14:16 ` Zack Weinberg
2022-12-14 17:36 ` Paolo Bonzini
2022-12-29 7:09 ` Zack Weinberg
2022-12-29 19:32 ` “Undefined behavior” considered harmful (was Re: Bug 29863 - Segmentation fault in memcmp-sse2.S…) Zack Weinberg
2022-12-29 22:20 ` Andreas Schwab [this message]
2022-12-30 13:28 ` Florian Weimer
2022-12-30 15:09 ` Florian Weimer
2022-12-13 22:52 ` Bug 29863 - Segmentation fault vs invalid results, memory models, and control/data dependencies Carlos O'Donell
2022-12-14 12:03 ` Florian Weimer
2022-12-13 21:20 ` Bug 29863 - Segmentation fault in memcmp-sse2.S if memory contents can concurrently change Florian Weimer
2022-12-13 22:59 ` Noah Goldstein
2022-12-14 12:06 ` Florian Weimer
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=87y1qp97j4.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=zack@owlfolio.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).