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 ipa/103267] Wrong code with ipa-sra Date: Tue, 30 Nov 2021 17:45:51 +0000 [thread overview] Message-ID: <bug-103267-4-M5BCj9jLVS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103267-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103267 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Jambor <jamborm@gcc.gnu.org>: https://gcc.gnu.org/g:e5440bc08e07fd491dcccd47e1b86a5985ee117c commit r12-5633-ge5440bc08e07fd491dcccd47e1b86a5985ee117c Author: Martin Jambor <mjambor@suse.cz> Date: Tue Nov 30 18:45:11 2021 +0100 ipa-sra: Check also ECF_LOOPING_CONST_OR_PURE when evaluating calls in PR 103267 Honza found out that IPA-SRA does not look at ECF_LOOPING_CONST_OR_PURE when evaluating if a call can have side effects. Fixed with this patch. The testcase infinitely loops in a const function, so it would not make a good addition to the testsuite. gcc/ChangeLog: 2021-11-29 Martin Jambor <mjambor@suse.cz> PR ipa/103267 * ipa-sra.c (scan_function): Also check ECF_LOOPING_CONST_OR_PURE flag.
next prev parent reply other threads:[~2021-11-30 17:45 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-15 22:02 [Bug ipa/103267] New: " hubicka at gcc dot gnu.org 2021-11-16 7:58 ` [Bug ipa/103267] " marxin at gcc dot gnu.org 2021-11-16 8:26 ` hubicka at gcc dot gnu.org 2021-11-16 8:31 ` marxin at gcc dot gnu.org 2021-11-16 8:34 ` marxin at gcc dot gnu.org 2021-11-16 8:42 ` Jan Hubicka 2021-11-16 8:43 ` hubicka at kam dot mff.cuni.cz 2021-11-16 8:47 ` Jan Hubicka 2021-11-16 8:48 ` hubicka at kam dot mff.cuni.cz 2021-11-16 8:48 ` marxin at gcc dot gnu.org 2021-11-16 8:54 ` Jan Hubicka 2021-11-16 8:48 ` marxin at gcc dot gnu.org 2021-11-16 8:50 ` marxin at gcc dot gnu.org 2021-11-16 8:54 ` hubicka at kam dot mff.cuni.cz 2021-11-30 14:31 ` jamborm at gcc dot gnu.org 2021-11-30 17:45 ` cvs-commit at gcc dot gnu.org [this message] 2021-12-01 13:24 ` cvs-commit at gcc dot gnu.org 2021-12-01 13:27 ` cvs-commit at gcc dot gnu.org 2021-12-01 17:30 ` cvs-commit at gcc dot gnu.org 2021-12-01 17:33 ` jamborm 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-103267-4-M5BCj9jLVS@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).