public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97981] [11 regression] 32-bit x86 'gcc.dg/atomic/c11-atomic-exec-1.c' execution test Date: Fri, 04 Dec 2020 13:54:54 +0000 [thread overview] Message-ID: <bug-97981-4-8LoNyIC0Vr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97981-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97981 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org, | |muecker at gwdg dot de Known to fail| |11.0 Known to work| |10.2.0 Keywords|needs-bisection | See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=98029 --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- Confirmed, started with r11-5188-g32934a4f45a72144. There's reduced test-case: $ cat atomic.i int main(void) { static volatile _Atomic(double) a, b = (double)((0)); if ((a = b) != ((double)((0)))) __builtin_abort(); return 0; } $ gcc -g atomic.i -m32 -c -O2 && gcc-10 -m32 -latomic atomic.o && valgrind ./a.out ==2400== Memcheck, a memory error detector ==2400== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==2400== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info ==2400== Command: ./a.out ==2400== ==2400== Conditional jump or move depends on uninitialised value(s) ==2400== at 0x8049081: main (atomic.i:3) ==2400== ==2400== Conditional jump or move depends on uninitialised value(s) ==2400== at 0x8049087: main (atomic.i:3) ==2400== ==2400== ==2400== Process terminating with default action of signal 6 (SIGABRT): dumping core ==2400== at 0x40C17D6: raise (in /lib/libc-2.32.so) ==2400== by 0x40A9313: abort (in /lib/libc-2.32.so) ==2400== by 0x8049054: main.cold (atomic.i:4) ==2400== by 0x40AAF75: (below main) (in /lib/libc-2.32.so) ==2400== ==2400== HEAP SUMMARY: ==2400== in use at exit: 0 bytes in 0 blocks ==2400== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==2400== ==2400== All heap blocks were freed -- no leaks are possible ==2400== ==2400== Use --track-origins=yes to see where uninitialised values come from ==2400== For lists of detected and suppressed errors, rerun with: -s ==2400== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) Aborted (core dumped)
next prev parent reply other threads:[~2020-12-04 13:54 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-25 7:52 [Bug regression/97981] New: " tschwinge at gcc dot gnu.org 2020-11-25 8:39 ` [Bug target/97981] " rguenth at gcc dot gnu.org 2020-12-04 13:54 ` marxin at gcc dot gnu.org [this message] 2020-12-04 13:58 ` [Bug target/97981] [11 regression] 32-bit x86 'gcc.dg/atomic/c11-atomic-exec-1.c' execution test since r11-5188-g32934a4f45a72144 marxin at gcc dot gnu.org 2020-12-04 15:33 ` muecker at gwdg dot de 2020-12-07 22:57 ` cvs-commit at gcc dot gnu.org 2021-01-21 16:39 ` jakub 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-97981-4-8LoNyIC0Vr@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: linkBe 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).