public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <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: Mon, 06 Dec 2021 16:19:11 +0000 [thread overview]
Message-ID: <bug-103466-4-OJFSmTQo1B@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
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:
https://gcc.gnu.org/g:70b043845d7c378c6a9361a6769885897d1018c2
commit r12-5806-g70b043845d7c378c6a9361a6769885897d1018c2
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Tue Nov 30 05:31:26 2021 -0800
libsanitizer: Use SSE to save and restore XMM registers
Use SSE, instead of AVX, to save and restore XMM registers to support
processors without AVX. The affected codes are unused in upstream since
https://github.com/llvm/llvm-project/commit/66d4ce7e26a5
and will be removed in
https://reviews.llvm.org/D112604
This fixed
FAIL: g++.dg/tsan/pthread_cond_clockwait.C -O0 execution test
FAIL: g++.dg/tsan/pthread_cond_clockwait.C -O2 execution test
on machines without AVX.
PR sanitizer/103466
* tsan/tsan_rtl_amd64.S (__tsan_trace_switch_thunk): Replace
vmovdqu with movdqu.
(__tsan_report_race_thunk): Likewise.
next prev parent reply other threads:[~2021-12-06 16:19 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
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 [this message]
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-OJFSmTQo1B@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).