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/103636] [12 Regression] Clang build fails with -flto -fno-strict-aliaisng -flifetime-dse=1 -fprofile-generate Date: Mon, 13 Dec 2021 13:58:47 +0000 [thread overview] Message-ID: <bug-103636-4-ykLGH7VvHO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103636-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103636 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:9eb8785b3fa3a180bd216cf68b53f1621628efc6 commit r12-5931-g9eb8785b3fa3a180bd216cf68b53f1621628efc6 Author: Martin Liska <mliska@suse.cz> Date: Fri Dec 10 11:40:54 2021 +0100 inline: fix ICE with -fprofile-generate PR ipa/103636 gcc/ChangeLog: * ipa-inline.c (can_inline_edge_p): Move logic checking no_profile_instrument_function logic to ... (can_early_inline_edge_p): ... here.
next prev parent reply other threads:[~2021-12-13 13:58 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-09 19:24 [Bug ipa/103636] New: " hubicka at gcc dot gnu.org 2021-12-09 19:27 ` [Bug ipa/103636] " hubicka at gcc dot gnu.org 2021-12-09 19:34 ` marxin at gcc dot gnu.org 2021-12-09 19:37 ` marxin at gcc dot gnu.org 2021-12-09 19:49 ` hubicka at gcc dot gnu.org 2021-12-10 0:31 ` [Bug ipa/103636] [12 Regression] " pinskia at gcc dot gnu.org 2021-12-10 10:24 ` marxin at gcc dot gnu.org 2021-12-10 10:28 ` marxin at gcc dot gnu.org 2021-12-10 10:36 ` hubicka at kam dot mff.cuni.cz 2021-12-13 13:58 ` cvs-commit at gcc dot gnu.org [this message] 2021-12-13 13:59 ` marxin 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-103636-4-ykLGH7VvHO@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).