public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tomas.kalibera at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105198] [9/10 Regression] Wrong code for C loop (GCC 12 -O2, GCC 11 -O3) Date: Fri, 08 Apr 2022 17:06:56 +0000 [thread overview] Message-ID: <bug-105198-4-0tbYuuKdhq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105198-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105198 --- Comment #11 from Tomas Kalibera <tomas.kalibera at gmail dot com> --- Thanks for the very quick fix! I confirm that when R is built with the fixed version of GCC 12, the R testcase for MASS is fixed, it works with -O2.
next prev parent reply other threads:[~2022-04-08 17:06 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-07 17:02 [Bug middle-end/105198] New: " tomas.kalibera at gmail dot com 2022-04-08 8:32 ` [Bug tree-optimization/105198] [11/12 Regression] " rguenth at gcc dot gnu.org 2022-04-08 8:45 ` jakub at gcc dot gnu.org 2022-04-08 9:04 ` rguenth at gcc dot gnu.org 2022-04-08 9:12 ` rguenth at gcc dot gnu.org 2022-04-08 10:55 ` rguenth at gcc dot gnu.org 2022-04-08 12:10 ` [Bug tree-optimization/105198] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-04-08 12:18 ` cvs-commit at gcc dot gnu.org 2022-04-08 12:20 ` [Bug tree-optimization/105198] [9/10/11 " rguenth at gcc dot gnu.org 2022-04-08 13:00 ` cvs-commit at gcc dot gnu.org 2022-04-08 13:00 ` [Bug tree-optimization/105198] [9/10 " rguenth at gcc dot gnu.org 2022-04-08 17:06 ` tomas.kalibera at gmail dot com [this message] 2022-05-06 12:47 ` cvs-commit at gcc dot gnu.org 2022-05-27 9:53 ` [Bug tree-optimization/105198] [9 " 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-105198-4-0tbYuuKdhq@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).