public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107209] [13 Regression] ICE: verify_gimple failed (error: statement marked for throw, but doesn't)
Date: Tue, 11 Oct 2022 15:57:14 +0000	[thread overview]
Message-ID: <bug-107209-4-LqHy82C7Te@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107209-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107209

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2022-10-11
             Status|UNCONFIRMED                 |NEW

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> Looks like EVRP elimination fails to clean EH?  Or target folding.  Would be
> nice to have a testcase not requiring aarch64 intrinsics.

I tried but didn't crash.
```
#define vector __attribute__((vector_size(sizeof(double))))

vector double
foo1 (void)
{
  double v1 = 3.14159265359;
  double v2 = 1.383894;
  double vec_1_data[] = {v1};
  double vec_2_data[] = {v2};
  vector double vec_1 = {vec_1_data[0]};
  vector double vec_2 = {vec_2_data[0]};

  return vec_1*vec_2;
}
```

Before evrp on the working testcase:
```
  vec_1_data$0_3 = 3.14159265359000006156975359772332012653350830078125e+0;
  vec_2_data$0_4 = 1.3838939999999999574953335468308068811893463134765625e+0;
  _1 = vec_1_data$0_3;
  vec_1_9 = {_1};
  _2 = vec_2_data$0_4;
  vec_2_11 = {_2};
  [LP 1] _12 = vec_1_9 * vec_2_11;
```

But with the aarch64 intrinsics:
  vec_1_data$0_2 = 3.14159265359000006156975359772332012653350830078125e+0;
  vec_2_data$0_3 = 1.3838939999999999574953335468308068811893463134765625e+0;
  _10 = vec_1_data$0_2;
  _7 = {_10};
  _20 = vec_2_data$0_3;
  _21 = {_20};
  [LP 1] # .MEM_28 = VDEF <.MEM_4(D)>
  # USE = nonlocal escaped 
  # CLB = nonlocal escaped 
  _24 = __builtin_aarch64_fmulxdf (_10, _20);
```

aarch64_general_gimple_fold_builtin inside aarch64-builtins.cc which does the
folding and it looks correct.
`BUILTIN_GPF (BINOP, fmulx, 0, ALL)`

So it requires aarch64 intrinsics.
In GCC 12, the folding of fmulxdf or the multiply didn't happen during evrp
even.

  parent reply	other threads:[~2022-10-11 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11  4:29 [Bug tree-optimization/107209] New: " asolokha at gmx dot com
2022-10-11  7:27 ` [Bug tree-optimization/107209] " rguenth at gcc dot gnu.org
2022-10-11 15:57 ` pinskia at gcc dot gnu.org [this message]
2022-10-18  8:08 ` rguenth at gcc dot gnu.org
2022-10-18  8:29 ` [Bug target/107209] " rguenth at gcc dot gnu.org
2022-11-30 17:26 ` jakub at gcc dot gnu.org
2022-12-20  9:22 ` ktkachov at gcc dot gnu.org
2022-12-20  9:29 ` jakub at gcc dot gnu.org
2023-01-13 10:01 ` cvs-commit at gcc dot gnu.org
2023-01-13 10:09 ` rsandifo 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-107209-4-LqHy82C7Te@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).