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 middle-end/63311] [9/10/11/12 Regression] -O1 optimization introduces valgrind warning Date: Thu, 17 Feb 2022 02:41:43 +0000 [thread overview] Message-ID: <bug-63311-4-SVU18ThhCS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63311-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63311 --- Comment #21 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>: https://gcc.gnu.org/g:5fbcbcaff7248604e04b39464f4fbd64fbf6e43b commit r12-7270-g5fbcbcaff7248604e04b39464f4fbd64fbf6e43b Author: David Malcolm <dmalcolm@redhat.com> Date: Wed Feb 16 18:21:58 2022 -0500 analyzer: const functions have no side effects [PR104576] PR analyzer/104576 tracks that we issue a false positive from -Wanalyzer-use-of-uninitialized-value for the reproducers of PR 63311 when optimization is disabled. The root cause is that the analyzer was considering that a call to __builtin_sinf could have side-effects. This patch fixes things by generalizing the handling for "pure" functions to also consider "const" functions. gcc/analyzer/ChangeLog: PR analyzer/104576 * region-model.cc: Include "calls.h". (region_model::on_call_pre): Use flags_from_decl_or_type to generalize check for DECL_PURE_P to also check for ECF_CONST. gcc/testsuite/ChangeLog: PR analyzer/104576 * gcc.dg/analyzer/torture/uninit-pr63311.c: New test. * gcc.dg/analyzer/uninit-pr104576.c: New test. * gfortran.dg/analyzer/uninit-pr63311.f90: New test. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2022-02-17 2:41 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-19 15:03 [Bug middle-end/63311] New: [4.9/5 " Joost.VandeVondele at mat dot ethz.ch 2014-09-22 10:24 ` [Bug middle-end/63311] " rguenth at gcc dot gnu.org 2014-09-22 10:24 ` rguenth at gcc dot gnu.org 2014-09-22 10:34 ` dominiq at lps dot ens.fr 2014-10-09 9:45 ` jakub at gcc dot gnu.org 2014-10-30 10:42 ` jakub at gcc dot gnu.org 2014-10-31 9:30 ` Joost.VandeVondele at mat dot ethz.ch 2014-10-31 9:34 ` Joost.VandeVondele at mat dot ethz.ch 2014-11-24 13:27 ` rguenth at gcc dot gnu.org 2014-11-24 13:54 ` Joost.VandeVondele at mat dot ethz.ch 2015-06-26 20:12 ` [Bug middle-end/63311] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:36 ` jakub at gcc dot gnu.org 2021-05-14 9:47 ` [Bug middle-end/63311] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:06 ` rguenth at gcc dot gnu.org 2022-02-15 12:09 ` mark at gcc dot gnu.org 2022-02-16 22:49 ` dmalcolm at gcc dot gnu.org 2022-02-17 2:41 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-27 9:35 ` [Bug middle-end/63311] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:31 ` jakub at gcc dot gnu.org 2023-07-07 10:30 ` [Bug middle-end/63311] [11/12/13/14 " rguenth at gcc dot gnu.org 2023-09-03 3:39 ` [Bug middle-end/63311] [11/12 " pinskia 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-63311-4-SVU18ThhCS@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).