public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100182] [8/9/10/11/12 Regression] Miscompilation of atomic_float/1.cc and atomic_float/wait_notify.cc on i686
Date: Mon, 19 Jul 2021 13:08:15 +0000 [thread overview]
Message-ID: <bug-100182-4-rgGsPkI68S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100182-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100182
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #28 from H.J. Lu <hjl.tools at gmail dot com> ---
29_atomics/atomic_ref/wait_notify.c has the same issue on Linux/x86-64 with
-m32:
(gdb) bt
#0 0xf7f5455d in __kernel_vsyscall ()
#1 0xf7b3a46b in syscall () from /lib/libc.so.6
#2 0x0804995d in std::__detail::__platform_wait<int> (
__addr=0x804d480 <std::__detail::__waiter_pool_base::_S_for(void
const*)::__w+960>, __val=1)
at
/export/users/hjl/build/gnu/tools-build/gcc-gitlab-native/build-x86_64-linux/x86_64-pc-linux-gnu/32/libstdc++-v3/include/bits/atomic_wait.h:104
#3 0x08049afa in std::__detail::__waiter_pool::_M_do_wait (__old=1,
__addr=0x804d480 <std::__detail::__waiter_pool_base::_S_for(void
const*)::__w+960>, this=<optimized out>)
at
/export/users/hjl/build/gnu/tools-build/gcc-gitlab-native/build-x86_64-linux/x86_64-pc-linux-gnu/32/libstdc++-v3/include/bits/atomic_wait.h:261
#4 std::__detail::__waiter<std::integral_constant<bool, true>
>::_M_do_wait_v<int, std::__atomic_impl::wait<int>(int const*,
std::remove_volatile<int>::type, std::memory_order)::{lambda()#1}>(int,
std::__atomic_impl::wait<int>(int const*, std::remove_volatile<int>::type,
std::memory_order)::{lambda()#1}) (__vfn=...,
__old=42, this=<synthetic pointer>)
at
/export/users/hjl/build/gnu/tools-build/gcc-gitlab-native/build-x86_64-linux/x86_64-pc-linux-gnu/32/libstdc++-v3/include/bits/atomic_wait.h:400
#5 std::__atomic_wait_address_v<int, std::__atomic_impl::wait<int>(int const*,
std::remove_volatile<int>::type, std::memory_order)::{lambda()#1}>(int const*,
int, std::__atomic_impl::wait<int>(int const*, std::remove_volatile<int>::type,
std::memory_order)::{lambda()#1}) (__addr=0xffaf629c, __old=42, __vfn=...)
--Type <RET> for more, q to quit, c to continue without paging--
at
/export/users/hjl/build/gnu/tools-build/gcc-gitlab-native/build-x86_64-linux/x86_64-pc-linux-gnu/32/libstdc++-v3/include/bits/atomic_wait.h:430
#6 0x08049bb2 in std::__atomic_impl::wait<int> (
__m=std::memory_order::seq_cst, __old=<optimized out>,
__ptr=<optimized out>)
at
/export/users/hjl/build/gnu/tools-build/gcc-gitlab-native/build-x86_64-linux/x86_64-pc-linux-gnu/32/libstdc++-v3/include/bits/atomic_base.h:1018
#7 std::__atomic_ref<int, true, false>::wait (__m=std::memory_order::seq_cst,
__old=<optimized out>, this=0xffaf62a4)
at
/export/users/hjl/build/gnu/tools-build/gcc-gitlab-native/build-x86_64-linux/x86_64-pc-linux-gnu/32/libstdc++-v3/include/bits/atomic_base.h:1570
#8 test<int> (va=0, vb=42)
at
/export/gnu/import/git/gitlab/x86-gcc/libstdc++-v3/testsuite/29_atomics/atomic_ref/wait_notify.cc:44
#9 0x08049250 in main ()
at
/export/gnu/import/git/gitlab/x86-gcc/libstdc++-v3/testsuite/29_atomics/atomic_ref/wait_notify.cc:52
(gdb)
when GCC is configured with
--enable-cet --with-demangler-in-ld --prefix=/usr/gcc-12.0.0-native
--with-local-prefix=/usr/local --enable-gnu-indirect-function
--enable-clocale=gnu --with-system-zlib --with-target-system-zlib
--with-fpmath=sse --with-arch=native --with-cpu=native
--enable-languages=c,c++,fortran,lto,objc,ada,obj-c++,go
where native == skylake-avx512. It happens one out of ~10 runs.
next prev parent reply other threads:[~2021-07-19 13:08 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 12:35 [Bug target/100182] New: [8/9/10/11/12 Regression] Miscompilation of atomic_float/1.cc " jakub at gcc dot gnu.org
2021-04-21 12:35 ` [Bug target/100182] " jakub at gcc dot gnu.org
2021-04-21 14:23 ` jakub at gcc dot gnu.org
2021-04-21 15:35 ` jakub at gcc dot gnu.org
2021-04-21 15:41 ` jakub at gcc dot gnu.org
2021-04-21 15:42 ` jakub at gcc dot gnu.org
2021-04-22 8:28 ` jakub at gcc dot gnu.org
2021-04-22 13:10 ` [Bug target/100182] [8/9/10/11/12 Regression] Miscompilation of atomic_float/1.cc and atomic_float/wait_notify.cc " cvs-commit at gcc dot gnu.org
2021-04-22 13:10 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:53 ` ubizjak at gmail dot com
2021-04-22 17:58 ` jakub at gcc dot gnu.org
2021-04-22 18:09 ` ubizjak at gmail dot com
2021-04-22 18:41 ` ubizjak at gmail dot com
2021-04-23 6:13 ` ubizjak at gmail dot com
2021-04-23 7:40 ` jakub at gcc dot gnu.org
2021-04-23 7:52 ` ubizjak at gmail dot com
2021-04-23 7:54 ` ubizjak at gmail dot com
2021-04-23 7:56 ` jakub at gcc dot gnu.org
2021-04-23 8:02 ` ubizjak at gmail dot com
2021-04-23 8:13 ` ubizjak at gmail dot com
2021-04-23 8:25 ` jakub at gcc dot gnu.org
2021-04-23 8:36 ` jakub at gcc dot gnu.org
2021-04-23 8:41 ` jakub at gcc dot gnu.org
2021-04-23 9:20 ` ubizjak at gmail dot com
2021-04-23 15:30 ` cvs-commit at gcc dot gnu.org
2021-04-28 10:44 ` cvs-commit at gcc dot gnu.org
2021-04-28 13:33 ` cvs-commit at gcc dot gnu.org
2021-04-28 18:02 ` cvs-commit at gcc dot gnu.org
2021-04-28 18:02 ` cvs-commit at gcc dot gnu.org
2021-04-28 18:09 ` ubizjak at gmail dot com
2021-07-19 13:08 ` hjl.tools at gmail dot com [this message]
2021-07-19 14:40 ` ubizjak at gmail dot com
2021-07-19 22:06 ` hjl.tools at gmail dot com
2021-07-19 22:18 ` ubizjak at gmail dot com
2021-07-20 4:23 ` cvs-commit at gcc dot gnu.org
2021-07-20 4:30 ` cvs-commit at gcc dot gnu.org
2021-07-20 4:36 ` cvs-commit at gcc dot gnu.org
2021-07-20 4:39 ` cvs-commit at gcc dot gnu.org
2021-07-20 4:41 ` ubizjak at gmail dot com
2021-07-31 19:24 ` hjl.tools at gmail dot com
2021-08-03 18:14 ` hjl.tools at gmail dot com
2021-08-03 18:24 ` ubizjak at gmail dot com
2021-08-03 18:30 ` hjl.tools at gmail dot com
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-100182-4-rgGsPkI68S@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).