public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dvyukov at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/103466] [12 Regression] SIGILL on machine without avx support when using thread sanitizer
Date: Tue, 30 Nov 2021 03:44:51 +0000 [thread overview]
Message-ID: <bug-103466-4-XEBFyWcQfb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103466-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103466
Dmitry Vyukov <dvyukov at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dvyukov at google dot com
--- Comment #4 from Dmitry Vyukov <dvyukov at google dot com> ---
I guess I needed to use MOVDQU, but this code is unused since
https://github.com/llvm/llvm-project/commit/66d4ce7e26a5 and will be removed in
https://reviews.llvm.org/D112604
next prev parent reply other threads:[~2021-11-30 3:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 15:23 [Bug sanitizer/103466] New: SIGILL due to use of vmovdqu, thread sanitizer build pjfloyd at wanadoo dot fr
2021-11-29 15:26 ` [Bug sanitizer/103466] " marxin at gcc dot gnu.org
2021-11-30 1:13 ` [Bug sanitizer/103466] [12 Regression] SIGILL due to use of vmovdqu when using thread sanitizer (merge from upstream) pinskia at gcc dot gnu.org
2021-11-30 1:21 ` [Bug sanitizer/103466] [12 Regression] SIGILL on machine without avx support when using thread sanitizer pinskia at gcc dot gnu.org
2021-11-30 1:22 ` pinskia at gcc dot gnu.org
2021-11-30 1:26 ` pinskia at gcc dot gnu.org
2021-11-30 3:44 ` dvyukov at google dot com [this message]
2021-11-30 7:02 ` rguenth at gcc dot gnu.org
2021-11-30 13:47 ` marxin at gcc dot gnu.org
2021-12-06 15:44 ` jakub at gcc dot gnu.org
2021-12-06 15:57 ` hjl.tools at gmail dot com
2021-12-06 16:19 ` cvs-commit at gcc dot gnu.org
2021-12-09 13:07 ` marxin at gcc dot gnu.org
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=bug-103466-4-XEBFyWcQfb@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).