From: Richard Biener <richard.guenther@gmail.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: Richard Biener <rguenther@suse.de>,
GCC Patches <gcc-patches@gcc.gnu.org>,
d@dcepelik.cz
Subject: Re: Teach same_types_for_tbaa to structurally compare arrays, pointers and vectors
Date: Wed, 29 May 2019 13:31:00 -0000 [thread overview]
Message-ID: <CAFiYyc3Dm2pM2mHV-Ab1AXb+pSHNHPojCwmjQ_ocwno+9jvZTQ@mail.gmail.com> (raw)
In-Reply-To: <20190529132057.ivcrg3upxubuaazh@kam.mff.cuni.cz>
On Wed, May 29, 2019 at 3:21 PM Jan Hubicka <hubicka@ucw.cz> wrote:
>
> >
> > Please also see if there are testcases that do anything meaningful
> > and FAIL after instead of
> >
> > /* Do access-path based disambiguation. */
> > if (ref1 && ref2
> > && (handled_component_p (ref1) || handled_component_p (ref2)))
> >
> > doing
> >
> > /* Do access-path based disambiguation. */
> > if (ref1 && ref2
> > && (handled_component_p (ref1) && handled_component_p (ref2)))
> >
> On tramp3d we get quite few matches which are attached. If ref1 is
> MEM_REF and ref2 has non-trivial access path then it seems we need:
> 1) ref1 and ref2 to conflict (ref1 is a record or alias set 0)
> 2) basetype2 to contain ref1 (so it conflicts too)
> 3) if ref1 is a record than the access path may go into a type
> contained as field of ref1 but via path not containing ref1 itself.
>
> I tried to construct testcase:
>
> truct foo {int val;} *fooptr;
> struct bar {struct foo foo; int val2;} *barptr;
> int test()
> {
> struct foo foo={0};
> barptr->val2 = 1;
> *fooptr=foo;
> return barptr->val2;
> }
>
> but we do not optimize it. I.e. optimized dump has:
>
> test ()
> {
> struct bar * barptr.0_1;
> struct foo * fooptr.1_2;
> int _6;
>
> <bb 2> [local count: 1073741824]:
> barptr.0_1 = barptr;
> barptr.0_1->val2 = 1;
> fooptr.1_2 = fooptr;
> MEM[(struct foo *)fooptr.1_2] = 0;
> _6 = barptr.0_1->val2;
> return _6;
> }
>
> I see no reason why we should not constant propagate the return value.
Indeed a good example. Make it work and add it to the testsuite ;)
I would have said get_alias_set () on the ref type should already have
disambiguated 'int' (barptr->val2) from *fooptr (struct foo) but of course
they conflict because foo contains 'int'.
I guess it doesn't work because 'struct foo' isn't part of the other
path. Here nonoverlapping_component_refs_of_decl_p would be
the vehicle to use (but IIRC that would also require a common
type in one of both paths).
Richard.
>
> Honza
next prev parent reply other threads:[~2019-05-29 13:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 11:14 Jan Hubicka
2019-05-24 12:57 ` Richard Biener
2019-05-24 13:19 ` Jan Hubicka
2019-05-27 7:16 ` Richard Biener
2019-05-27 8:32 ` Jan Hubicka
2019-05-29 12:28 ` Richard Biener
2019-05-29 13:24 ` Jan Hubicka
2019-05-29 13:31 ` Richard Biener [this message]
2019-05-29 14:13 ` Jan Hubicka
2019-05-30 16:23 ` Martin Jambor
[not found] ` <alpine.LSU.2.20.1905311402280.10704@zhemvz.fhfr.qr>
[not found] ` <ri6blzdaer9.fsf@suse.cz>
[not found] ` <alpine.LSU.2.20.1906061503090.10704@zhemvz.fhfr.qr>
2019-06-06 16:00 ` Martin Jambor
2019-05-29 20:00 ` Jan Hubicka
2019-05-31 12:50 ` Richard Biener
2019-05-27 13:57 ` Jan Hubicka
2019-05-29 12:33 ` Richard Biener
2019-05-29 12:36 ` Jan Hubicka
2019-05-29 12:56 ` Richard Biener
2019-05-29 13:32 ` Jan Hubicka
2019-05-24 13:48 ` Jan Hubicka
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=CAFiYyc3Dm2pM2mHV-Ab1AXb+pSHNHPojCwmjQ_ocwno+9jvZTQ@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=d@dcepelik.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=rguenther@suse.de \
/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).