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 fortran/97652] New pdt14 failure after g:617695cdc2b3d950f1e4deb5ea85d5cc302943f4
Date: Sat, 31 Oct 2020 08:18:20 +0000 [thread overview]
Message-ID: <bug-97652-4-DogB3xdqdS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97652-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97652
--- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Actually there is another propagation happening in ipa-cp analysis:
--- aa/pdt_14.f03.077i.cp 2020-10-31 09:00:52.809726530 +0100
+++ pdt_14.f03.077i.cp 2020-10-31 09:10:35.204755828 +0100
@@ -10,6 +10,8 @@
Starting walk at: push_8 (&root, &C.4104);
instance pointer: &root Outer instance pointer: root offset: 0 (bits) vtbl
reference:
Function call may change dynamic type:push_8 (&root, &C.4103);
+ipa-modref: call stmt push_8 (&root, &C.4103);
+ipa-modref: call to push_8/6 does not clobber ref: root alias sets: 14->14
Determining dynamic type for call: push_8 (&root, &C.4104);
Starting walk at: push_8 (&root, &C.4104);
instance pointer: &C.4104 Outer instance pointer: C.4104 offset: 0 (bits)
vtbl reference:
@@ -19,6 +21,10 @@
instance pointer: &root Outer instance pointer: root offset: 0 (bits) vtbl
reference:
Function call may change dynamic type:push_8 (&root, &C.4104);
Function call may change dynamic type:push_8 (&root, &C.4103);
+ipa-modref: call stmt push_8 (&root, &C.4104);
+ipa-modref: call to push_8/6 does not clobber ref: root alias sets: 14->14
+ipa-modref: call stmt push_8 (&root, &C.4103);
+ipa-modref: call to push_8/6 does not clobber ref: root alias sets: 14->14
Determining dynamic type for call: push_8 (&root, &C.4105);
Starting walk at: push_8 (&root, &C.4105);
instance pointer: &C.4105 Outer instance pointer: C.4105 offset: 0 (bits)
vtbl reference:
@@ -30,6 +36,12 @@
Function call may change dynamic type:push_8 (&root, &C.4105);
Function call may change dynamic type:push_8 (&root, &C.4104);
Function call may change dynamic type:push_8 (&root, &C.4103);
+ipa-modref: call stmt push_8 (&root, &C.4105);
+ipa-modref: call to push_8/6 does not clobber ref: root alias sets: 14->14
+ipa-modref: call stmt push_8 (&root, &C.4104);
+ipa-modref: call to push_8/6 does not clobber ref: root alias sets: 14->14
+ipa-modref: call stmt push_8 (&root, &C.4103);
+ipa-modref: call to push_8/6 does not clobber ref: root alias sets: 14->14
Determining dynamic type for call: _3 = pop_8 (&root);
Starting walk at: _3 = pop_8 (&root);
instance pointer: &root Outer instance pointer: root offset: 0 (bits) vtbl
reference:
@@ -129,10 +141,14 @@
no arg info
callsite ch2701/7 -> pop_8/5 :
param 0: UNKNOWN
+ Aggregate passed by reference:
+ offset: 0, type: struct pdtlink_8 *, CONST: 0B
value: 0x0, mask: 0xfffffffffffffff8
VR [1, -1]
callsite ch2701/7 -> push_8/6 :
param 0: UNKNOWN
+ Aggregate passed by reference:
+ offset: 0, type: struct pdtlink_8 *, CONST: 0B
value: 0x0, mask: 0xfffffffffffffff8
VR [1, -1]
param 1: CONST: &C.4105 -> 3.0e+0
@@ -140,6 +156,8 @@
Unknown VR
callsite ch2701/7 -> push_8/6 :
param 0: UNKNOWN
+ Aggregate passed by reference:
+ offset: 0, type: struct pdtlink_8 *, CONST: 0B
value: 0x0, mask: 0xfffffffffffffff8
VR [1, -1]
param 1: CONST: &C.4104 -> 2.0e+0
The jump function is not used for cloning, only triggers inline, but the
conclusion seems wrong. push_8 can make root non-0. Root is of type pdtlink_8
so perhaps Frontend produces multiple copies of these.
push_8 store is:
- Analyzing store: *self_34(D)
- Recording base_set=8 ref_set=8 parm=0
so indeed a different alias set than 14 used by ch2701
next prev parent reply other threads:[~2020-10-31 8:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 8:05 [Bug fortran/97652] New: " hubicka at gcc dot gnu.org
2020-10-31 8:18 ` hubicka at gcc dot gnu.org [this message]
2020-11-02 11:30 ` [Bug fortran/97652] " hubicka at gcc dot gnu.org
2020-11-02 13:39 ` [Bug fortran/97652] [11 Regression] New gfortran.dg/pdt_14.f03 " rguenth at gcc dot gnu.org
2020-11-02 13:48 ` rguenth at gcc dot gnu.org
2020-11-02 13:56 ` rguenth at gcc dot gnu.org
2020-11-02 13:58 ` rguenth at gcc dot gnu.org
2020-11-02 14:25 ` rguenth at gcc dot gnu.org
2020-11-02 14:27 ` hubicka at ucw dot cz
2020-11-02 14:29 ` [Bug ipa/97652] " rguenth at gcc dot gnu.org
2020-11-02 14:29 ` rguenth at gcc dot gnu.org
2020-11-02 14:32 ` hubicka at ucw dot cz
2020-11-02 14:51 ` [Bug fortran/97652] " rguenth at gcc dot gnu.org
2020-11-02 14:52 ` rguenth at gcc dot gnu.org
2020-11-03 7:25 ` rguenth at gcc dot gnu.org
2020-11-03 11:15 ` rguenth at gcc dot gnu.org
2020-11-06 7:27 ` cvs-commit at gcc dot gnu.org
2020-11-06 13:01 ` rguenth at gcc dot gnu.org
2020-11-06 15:32 ` cvs-commit at gcc dot gnu.org
2020-11-06 16:57 ` 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-97652-4-DogB3xdqdS@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).