public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114203] [13 Regression] Miscompilation: A possible miscompilation in GCC 13 and 14 with option -Os Date: Thu, 21 Mar 2024 11:49:54 +0000 [thread overview] Message-ID: <bug-114203-4-qTlQsx6qlM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114203-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114203 --- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:a729b1227bc8c84cd91a3b8c9c9d11bc43d415de commit r13-8482-ga729b1227bc8c84cd91a3b8c9c9d11bc43d415de Author: Richard Biener <rguenther@suse.de> Date: Mon Mar 4 10:38:31 2024 +0100 tree-optimization/114203 - wrong CLZ niter computation For precision less than int we apply the adjustment to make it defined at zero after the adjustment to make it compute CLZ rather than CTZ. That's wrong. PR tree-optimization/114203 * tree-ssa-loop-niter.cc (build_cltz_expr): Apply CTZ->CLZ adjustment before making the result defined at zero. * gcc.dg/torture/pr114203.c: New testcase. (cherry picked from commit cde50296a19b109909089b91d532d2c8455f5f10)
next prev parent reply other threads:[~2024-03-21 11:49 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-02 4:19 [Bug c/114203] New: " 141242068 at smail dot nju.edu.cn 2024-03-02 4:40 ` [Bug tree-optimization/114203] [13/14 Regression] " pinskia at gcc dot gnu.org 2024-03-04 9:36 ` rguenth at gcc dot gnu.org 2024-03-04 10:45 ` cvs-commit at gcc dot gnu.org 2024-03-04 10:46 ` [Bug tree-optimization/114203] [13 " rguenth at gcc dot gnu.org 2024-03-21 11:49 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-21 11:51 ` 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-114203-4-qTlQsx6qlM@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).