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 c++/108390] ICE in fold_convert_loc, at fold-const.cc:2504 partial ordering between array types
Date: Fri, 13 Jan 2023 01:19:58 +0000	[thread overview]
Message-ID: <bug-108390-4-q70Ah1ugSo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108390-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-invalid-code
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2023-01-13
     Ever confirmed|0                           |1
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=79092

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I suspect the patch for PR79092 cahnged the behavior in GCC 8.

I don't see how this can't be ambiguous. It is odd that clang accepts it.

This C++20 testcase also causes the ICE and clang rejects it as ambiguous:

```
template<auto t> long f(int(*)[t], int(*)[t]);
template<int i> int f(int(*)[i], int(*)[i]);
int n = f<2>(0, 0);
```

So at least ICE on invalid.

  parent reply	other threads:[~2023-01-13  1:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13  0:47 [Bug c++/108390] New: " ed at catmur dot uk
2023-01-13  1:08 ` [Bug c++/108390] " pinskia at gcc dot gnu.org
2023-01-13  1:19 ` pinskia at gcc dot gnu.org [this message]
2023-01-13  8:15 ` [Bug c++/108390] ICE in fold_convert_loc, at fold-const.cc:2504 partial ordering between array types since r8-4678-g6296cf8e099aae43 marxin at gcc dot gnu.org
2023-01-13  9:24 ` [Bug c++/108390] [10/11/12/13 Regression] " jakub at gcc dot gnu.org
2023-03-22 19:30 ` cvs-commit at gcc dot gnu.org
2023-07-07 10:44 ` [Bug c++/108390] [11/12 " rguenth 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-108390-4-q70Ah1ugSo@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).