public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/65244] Bogus -Wmaybe-uninitialized warning with posix_memalign() and -Og Date: Wed, 31 Aug 2022 09:07:53 +0000 [thread overview] Message-ID: <bug-65244-4-GjpQPJMQwI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65244-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65244 --- Comment #17 from Richard Biener <rguenth at gcc dot gnu.org> --- OK, so the "optimization" is needed on the DEF side as extern void __attribute__((noreturn)) abort (void); int foo (int flag, int val) { int tem; if (flag) { if (val == 0) abort (); tem = val; } /* large - prevent jump threading */ __asm__ volatile ("\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"); if (flag) return tem; return 0; } shows (I'll add that testcase). Otherwise we pick up ((NOT (val_5(D) == 0)) AND (flag_3(D) != 0)) as the condition on which 'tem' is well-defined and the guard of the use is just ((flag_3(D) != 0))
next prev parent reply other threads:[~2022-08-31 9:07 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-27 18:51 [Bug c/65244] New: " ulfalizer at gmail dot com 2015-02-27 19:10 ` [Bug c/65244] " ulfalizer at gmail dot com 2015-02-27 21:02 ` manu at gcc dot gnu.org 2015-02-27 21:24 ` ulfalizer at gmail dot com 2015-02-27 21:48 ` manu at gcc dot gnu.org 2015-02-27 22:02 ` ulfalizer at gmail dot com 2015-02-27 22:07 ` howarth at bromo dot med.uc.edu 2015-02-27 23:04 ` ulfalizer at gmail dot com 2015-02-27 23:21 ` pinskia at gcc dot gnu.org 2015-02-28 1:24 ` manu at gcc dot gnu.org 2021-03-31 19:05 ` [Bug middle-end/65244] " msebor at gcc dot gnu.org 2022-08-30 8:27 ` [Bug tree-optimization/65244] " rguenth at gcc dot gnu.org 2022-08-31 9:07 ` rguenth at gcc dot gnu.org [this message] 2022-08-31 11:04 ` cvs-commit at gcc dot gnu.org 2022-08-31 11:04 ` rguenth 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-65244-4-GjpQPJMQwI@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).