public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: "Uecker, Martin" <Martin.Uecker@med.uni-goettingen.de>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: TBAA bug?
Date: Tue, 27 Jul 2021 10:05:26 +0200	[thread overview]
Message-ID: <CAFiYyc0-_QC07G+2=jLwhBmvCXb4fJY-FVzr-jvCCaQ=PpC+iA@mail.gmail.com> (raw)
In-Reply-To: <1a066477a05b80f7edb50d71c495f63c10e8e74a.camel@med.uni-goettingen.de>

On Sun, Jul 25, 2021 at 1:58 PM Uecker, Martin
<Martin.Uecker@med.uni-goettingen.de> wrote:
>
>
>
> Hi Richard,
>
> here is another case where it seems that TBAA goes
> wrong. Since this is not in a loop, it seems this
> is something else than what we discussed. Is
> this a known issue?

No, it's not known and it is a bug.  It seems to be
related to doing

Value numbering stmt = pu_6(D)->x = xy_7;
Store matched earlier value, value numbering store vdefs to matching vuses.
Setting value number of .MEM_8 to .MEM_5 (changed)

I'm looking into it.

Richard.

> Best,
> Martin
>
>
> #include <stdio.h>
> #include <stdlib.h>
>
> union u {
>   long x;
>   long long y;
> };
>
> __attribute__((noinline,noclone))
> long test(long *px, long long *py, union u *pu)
> {
>   *px = 0;
>   *py = 1;
>
>   long xy = pu->y;
>   pu->x = xy;
>
>   return *px;
> }
>
> int main(void)
> {
>   union u u;
>   printf("%ld\n", test(&u.x, &u.y, &u));
> }
>
> https://godbolt.org/z/a9drezEza
>

  parent reply	other threads:[~2021-07-27  8:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-25 11:58 Uecker, Martin
2021-07-27  8:02 ` Richard Biener
2021-07-27  8:05 ` Richard Biener [this message]
2021-07-27 12:08   ` Richard Biener

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='CAFiYyc0-_QC07G+2=jLwhBmvCXb4fJY-FVzr-jvCCaQ=PpC+iA@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=Martin.Uecker@med.uni-goettingen.de \
    --cc=gcc@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).