public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zhendong.su at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/97836] wrong code at -O1 on x86_64-pc-linux-gnu Date: Sun, 15 Nov 2020 12:53:03 +0000 [thread overview] Message-ID: <bug-97836-4-y09z2S9syi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97836-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97836 --- Comment #1 from Zhendong Su <zhendong.su at inf dot ethz.ch> --- Another related test that triggers the miscompilation at -Os, but not -O1: [621] % gcctk -O1 small.c; ./a.out [622] % [622] % gcctk -Os small.c; ./a.out Aborted [623] % [623] % cat small.c int a; int b(int c) { return 0; } static int *d(int *e) { if (a) { a = a && b(*e); } return e; } int main() { int f; if (d(&f) != &f) __builtin_abort(); return 0; }
next prev parent reply other threads:[~2020-11-15 12:53 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-15 9:49 [Bug rtl-optimization/97836] New: " zhendong.su at inf dot ethz.ch 2020-11-15 12:53 ` zhendong.su at inf dot ethz.ch [this message] 2020-11-15 13:19 ` [Bug rtl-optimization/97836] [11 Regression] wrong code at -O1 on x86_64-pc-linux-gnu by r11-5029 hjl.tools at gmail dot com 2020-11-15 13:33 ` hubicka at gcc dot gnu.org 2020-11-16 7:26 ` rguenth at gcc dot gnu.org 2020-11-16 7:46 ` hubicka at gcc dot gnu.org 2020-12-02 19:31 ` jakub at gcc dot gnu.org 2021-01-01 19:11 ` [Bug rtl-optimization/97836] " hubicka at gcc dot gnu.org 2021-03-29 10:21 ` hubicka at gcc dot gnu.org 2021-04-27 11:39 ` jakub at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2021-08-22 19:40 ` hubicka 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-97836-4-y09z2S9syi@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).