From: "Cristian Rodríguez" <crrodriguez@opensuse.org>
To: Narayanan Iyer <nars@yottadb.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Bug 29863 - Segmentation fault in memcmp-sse2.S if memory contents can concurrently change
Date: Tue, 13 Dec 2022 15:39:39 -0300 [thread overview]
Message-ID: <CAPBLoAcOXyjRVc2UpKwPteNxE9xq_ThAT7sTH_VUFqrBDMHKQQ@mail.gmail.com> (raw)
In-Reply-To: <0a1f01d90f1f$96c7ce60$c4576b20$@yottadb.com>
On Tue, Dec 13, 2022 at 3:20 PM Narayanan Iyer via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> Hi,
>
> I had created a glibc bug report at https://sourceware.org/bugzilla/show_bug.cgi?id=29863
>
It might as well make a shelter.. from pigs on the wing... That's UB
all the way.
next prev parent reply other threads:[~2022-12-13 18:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 18:20 Narayanan Iyer
2022-12-13 18:31 ` Andrew Pinski
2022-12-13 18:39 ` Narayanan Iyer
2022-12-13 18:39 ` Cristian Rodríguez [this message]
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
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
[not found] <PAWPR08MB89825887E12FF900540365F483E09@PAWPR08MB8982.eurprd08.prod.outlook.com>
[not found] ` <PAWPR08MB898260DA844D695EA70ED3E483E09@PAWPR08MB8982.eurprd08.prod.outlook.com>
2022-12-14 21:56 ` Wilco Dijkstra
2022-12-29 7:21 ` Zack Weinberg
2022-12-29 20:02 ` Alejandro Colomar
2022-12-30 18:02 ` Joseph Myers
2023-03-20 15:40 ` Zack Weinberg
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=CAPBLoAcOXyjRVc2UpKwPteNxE9xq_ThAT7sTH_VUFqrBDMHKQQ@mail.gmail.com \
--to=crrodriguez@opensuse.org \
--cc=libc-alpha@sourceware.org \
--cc=nars@yottadb.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).