public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/103211] [12 Regression] 416.gamess crashes after r12-5177-g494bdadf28d0fb35 Date: Fri, 12 Nov 2021 16:44:42 +0000 [thread overview] Message-ID: <bug-103211-4-wpMYEfGFel@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103211-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103211 --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- Optimized dump differs for couple of functions in the same way: diff -u good bad --- good 2021-11-12 17:42:36.995947103 +0100 +++ bad 2021-11-12 17:41:56.728194961 +0100 @@ -38,7 +38,6 @@ ;; Function abrt (abrt_, funcdef_no=10, decl_uid=4338, cgraph_uid=11, symbol_order=10) (executed once) -Removing basic block 5 __attribute__((fn spec (". "))) void abrt () { @@ -350,7 +349,6 @@ void setfm (integer(kind=4) * ipar) { <bb 2> [local count: 1073741824]: - master.0.setfm (0, ipar_2(D)); [tail call] return; } maybe the fnspec for master.0.setfm is bad? __attribute__((fn spec (". R w "))) void master.0.setfm (integer(kind=8) __entry, integer(kind=4) * ipar) {
next prev parent reply other threads:[~2021-11-12 16:44 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-12 13:15 [Bug ipa/103211] New: " marxin at gcc dot gnu.org 2021-11-12 13:15 ` [Bug ipa/103211] " marxin at gcc dot gnu.org 2021-11-12 13:16 ` rguenth at gcc dot gnu.org 2021-11-12 16:40 ` marxin at gcc dot gnu.org 2021-11-12 16:44 ` marxin at gcc dot gnu.org [this message] 2021-11-12 16:52 ` Jan Hubicka 2021-11-12 16:52 ` hubicka at kam dot mff.cuni.cz 2021-11-12 16:57 ` marxin at gcc dot gnu.org 2021-11-12 17:02 ` hubicka at gcc dot gnu.org 2021-11-13 23:49 ` cvs-commit at gcc dot gnu.org 2021-11-13 23:50 ` hubicka 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-103211-4-wpMYEfGFel@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).