public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102571] FAIL: libgomp.c/../libgomp.c-c++-common/atomic-21.c execution test Date: Wed, 06 Oct 2021 10:20:56 +0000 [thread overview] Message-ID: <bug-102571-4-lSAkELGnFp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102571-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102571 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Workaround committed, so for OpenMP it shouldn't trigger anymore. But for int foo (char *p) { long double l = 0.0; __builtin_clear_padding (&l); return __builtin_memcpy (&l, p, sizeof (l)); } it still can, similarly for <atomic> APIs on long double, _Complex long double etc. Related to PR93270 which was also about DSE, but the other order, something clearing the memory and then writing a long double over it (which due to hw leaves the padding bits unchanged) and DSE removing the clearing before it. Here it is a long double store of initializer_zerop followed by clearing of the padding bits and removes the clearing of the padding bits.
prev parent reply other threads:[~2021-10-06 10:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-02 22:56 [Bug libgomp/102571] New: " hjl.tools at gmail dot com 2021-10-04 19:19 ` [Bug tree-optimization/102571] " jakub at gcc dot gnu.org 2021-10-05 14:15 ` jakub at gcc dot gnu.org 2021-10-06 8:45 ` cvs-commit at gcc dot gnu.org 2021-10-06 10:20 ` jakub at gcc dot gnu.org [this message]
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-102571-4-lSAkELGnFp@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).