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 tree-optimization/103376] New: wrong code at -Os and above on x86_64-linux-gnu Date: Tue, 23 Nov 2021 08:22:12 +0000 [thread overview] Message-ID: <bug-103376-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103376 Bug ID: 103376 Summary: wrong code at -Os and above on x86_64-linux-gnu Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: zhendong.su at inf dot ethz.ch Target Milestone: --- It appears to be a recent regression. [603] % gcctk -v Using built-in specs. COLLECT_GCC=gcctk COLLECT_LTO_WRAPPER=/local/suz-local/software/local/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/12.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../gcc-trunk/configure --disable-bootstrap --prefix=/local/suz-local/software/local/gcc-trunk --enable-languages=c,c++ --disable-werror --enable-multilib --with-system-zlib Thread model: posix Supported LTO compression algorithms: zlib gcc version 12.0.0 20211123 (experimental) [master r12-5461-gcab8f69857d] (GCC) [604] % [604] % gcctk -O1 small.c; ./a.out [605] % [605] % gcctk -Os small.c [606] % ./a.out Aborted [607] % [607] % cat small.c int printf(const char *, ...); long long a = 7108473123; int b, c, *d; int main() { long long e, f; e = a; if (b) { printf("%d", c); d = 0; while (*d) ; } f = 0x88582324C7C1E17B; a = ~-(e ^ f ^ ~a) ^ ~18013; if (a > -8622102845723662559LL) __builtin_abort(); }
next reply other threads:[~2021-11-23 8:22 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-23 8:22 zhendong.su at inf dot ethz.ch [this message] 2021-11-23 8:30 ` [Bug tree-optimization/103376] [12 Regression] wrong code at -Os and above on x86_64-linux-gnu since r12-5453-ga944b5dec3adb28e marxin at gcc dot gnu.org 2021-11-23 10:41 ` jakub at gcc dot gnu.org 2021-11-23 11:01 ` jakub at gcc dot gnu.org 2021-11-23 11:06 ` jakub at gcc dot gnu.org 2021-11-23 13:17 ` jakub at gcc dot gnu.org 2021-11-24 2:02 ` pinskia at gcc dot gnu.org 2021-11-24 2:03 ` pinskia at gcc dot gnu.org 2021-11-24 7:09 ` zhendong.su at inf dot ethz.ch 2021-11-24 8:55 ` cvs-commit at gcc dot gnu.org 2021-11-24 8:56 ` jakub at gcc dot gnu.org 2021-11-24 14:15 ` roger at nextmovesoftware dot com 2021-11-25 9:40 ` cvs-commit at gcc dot gnu.org 2022-04-09 19:23 ` cvs-commit 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-103376-4@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).