public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mednafen at sent dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/113255] New: wrong code with -O2 -mtune=k8 Date: Sat, 06 Jan 2024 23:24:09 +0000 [thread overview] Message-ID: <bug-113255-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113255 Bug ID: 113255 Summary: wrong code with -O2 -mtune=k8 Product: gcc Version: 13.2.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: mednafen at sent dot com Target Milestone: --- Target: x86_64-pc-linux-gnu Created attachment 57000 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57000&action=edit test case Linux x86_64 $ /usr/local/gcc-13.2.0/bin/gcc -Wall -O2 -o sprite sprite.c && ./sprite 1 $ /usr/local/gcc-13.2.0/bin/gcc -Wall -O2 -mtune=k8 -o sprite sprite.c && ./sprite 0 Aborted The problem appears to have started around version 10.2.0.
next reply other threads:[~2024-01-06 23:24 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-06 23:24 mednafen at sent dot com [this message] 2024-01-06 23:53 ` [Bug target/113255] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2024-01-07 12:13 ` jakub at gcc dot gnu.org 2024-01-07 19:48 ` ubizjak at gmail dot com 2024-01-09 7:52 ` rguenth at gcc dot gnu.org 2024-01-09 7:58 ` jakub at gcc dot gnu.org 2024-01-09 8:00 ` ubizjak at gmail dot com 2024-01-09 9:27 ` jakub at gcc dot gnu.org 2024-01-09 10:20 ` rguenth at gcc dot gnu.org 2024-01-09 12:09 ` rguenth at gcc dot gnu.org 2024-01-10 8:57 ` rguenth at gcc dot gnu.org 2024-01-12 8:48 ` rguenth at gcc dot gnu.org 2024-01-23 7:08 ` cvs-commit at gcc dot gnu.org 2024-01-23 7:10 ` [Bug target/113255] [11/12/13 " rguenth at gcc dot gnu.org 2024-01-23 14:38 ` cvs-commit at gcc dot gnu.org 2024-02-01 12:53 ` rguenth at gcc dot gnu.org 2024-02-01 13:08 ` rguenth at gcc dot gnu.org 2024-02-05 7:35 ` 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-113255-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).