public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/103246] [12 Regression] 416.gamess miscompare with -O2 -g -flto=auto since r12-5223-gecdf414bd89e6ba251f6b3f494407139b4dbae0e
Date: Wed, 17 Nov 2021 13:03:05 +0000 [thread overview]
Message-ID: <bug-103246-4-mCRKVzsuyz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103246-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103246
--- Comment #16 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Building with LTO only ecpder.fppized.o and ecplib.fppized.o I get the failure
going away with --dbg-cnt=ipa_cp_values:10 and :9 works.
Different ipa-cp decision is
+***dbgcnt: upper limit 10 reached for ipa_cp_values.***
+ - Creating a specialized node of formdr/4 for all known contexts.
+ replacing param #5 int & restrict with const &ecpidx.iamin
+ replacing param #6 int & restrict with const &ecpidx.iamax
+ Removed a reference from formii.constprop/284 to ecpidx/11.
+ ...and replaced it with LOAD one.
+ Removed a reference from ecp2d/1 to ecpidx/11.
+ Removed a reference from ecp1d/0 to ecpidx/11.
+ replacing param #9 logical(kind=4) & restrict with const &ecpidx.norm -
forcing load reference
In modref the propagation goes same way and we update signature as follows:
+Updating summary for formdr.constprop/285 from:
+ loads:
+ Limits: 32 bases, 16 refs
+ Every base
+ stores:
+ Limits: 32 bases, 16 refs
+ Every base
+ Side effects
+ Nondeterministic
+ parm 0 flags: no_direct_clobber no_direct_escape no_indirect_escape
+ parm 1 flags: no_direct_clobber no_direct_escape no_indirect_escape
+ parm 2 flags: no_direct_escape no_indirect_escape
+ parm 3 flags: no_direct_escape no_indirect_escape
+ parm 4 flags: no_direct_escape no_indirect_escape
+ parm 5 flags: no_direct_clobber no_indirect_clobber no_direct_escape
no_indirect_escape no_indirect_read
+ parm 6 flags: no_direct_clobber no_indirect_clobber no_direct_escape
no_indirect_escape no_indirect_read
+ parm 7 flags: no_direct_clobber no_indirect_clobber no_direct_escape
no_indirect_escape no_indirect_read
+ parm 8 flags: no_direct_clobber no_indirect_clobber no_direct_escape
no_indirect_escape no_indirect_read
+ parm 9 flags: no_direct_clobber no_indirect_clobber no_direct_escape
no_indirect_escape no_indirect_read
+to:
+ loads:
+ Limits: 32 bases, 16 refs
+ Every base
+ stores:
+ Limits: 32 bases, 16 refs
+ Every base
+ Side effects
+ Nondeterministic
+ parm 0 flags: no_direct_clobber no_direct_escape no_indirect_escape
+ parm 1 flags: no_direct_clobber no_direct_escape no_indirect_escape
+ parm 2 flags: no_direct_escape no_indirect_escape
+ parm 3 flags: no_direct_escape no_indirect_escape
+ parm 4 flags: no_direct_escape no_indirect_escape
+ parm 5 flags: no_direct_clobber no_indirect_clobber no_direct_escape
no_indirect_escape no_indirect_read
+ parm 6 flags: no_direct_clobber no_indirect_clobber no_direct_escape
no_indirect_escape no_indirect_read
this changes partitioning decisions which makes quite a lot of fuzz in latr
dump files.
next prev parent reply other threads:[~2021-11-17 13:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 10:22 [Bug ipa/103246] New: " marxin at gcc dot gnu.org
2021-11-15 10:24 ` [Bug ipa/103246] " marxin at gcc dot gnu.org
2021-11-15 10:39 ` marxin at gcc dot gnu.org
2021-11-15 10:39 ` marxin at gcc dot gnu.org
2021-11-15 10:40 ` marxin at gcc dot gnu.org
2021-11-15 10:40 ` marxin at gcc dot gnu.org
2021-11-15 11:13 ` hubicka at gcc dot gnu.org
2021-11-16 16:09 ` jamborm at gcc dot gnu.org
2021-11-16 17:09 ` jamborm at gcc dot gnu.org
2021-11-16 19:24 ` marxin at gcc dot gnu.org
2021-11-16 19:34 ` marxin at gcc dot gnu.org
2021-11-16 20:53 ` marxin at gcc dot gnu.org
2021-11-16 22:42 ` hubicka at gcc dot gnu.org
2021-11-17 0:44 ` cvs-commit at gcc dot gnu.org
2021-11-17 9:11 ` marxin at gcc dot gnu.org
2021-11-17 9:38 ` hubicka at kam dot mff.cuni.cz
2021-11-17 12:27 ` hubicka at gcc dot gnu.org
2021-11-17 13:03 ` hubicka at gcc dot gnu.org [this message]
2021-11-17 13:15 ` hubicka at gcc dot gnu.org
2021-11-17 13:31 ` hubicka at gcc dot gnu.org
2021-11-17 18:58 ` hubicka at gcc dot gnu.org
2021-11-17 19:36 ` hubicka at gcc dot gnu.org
2021-11-17 21:06 ` cvs-commit at gcc dot gnu.org
2021-11-18 8:27 ` hubicka at gcc dot gnu.org
2021-11-18 8:28 ` hubicka at gcc dot gnu.org
2021-11-18 12:22 ` marxin at gcc dot gnu.org
2021-11-18 19:10 ` cvs-commit 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-103246-4-mCRKVzsuyz@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: link
Be 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).