public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/115476] [13/14/15 Regression] __has_unique_object_representation ICE with array of uninstantiated type of unknown bound Date: Thu, 13 Jun 2024 16:22:39 +0000 [thread overview] Message-ID: <bug-115476-4-9hqkGyaZ3z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115476-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115476 --- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Aha, so static_assert(__has_unique_object_representations(Foo<0>[])); is valid and should be treated just like static_assert(__has_unique_object_representations(Foo<0>)); but class Foo; static_assert(__has_unique_object_representations(Foo[])); is invalid, because 'Foo' is not a complete type.
next prev parent reply other threads:[~2024-06-13 16:22 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-13 15:08 [Bug c++/115476] New: " mital at mitalashok dot co.uk 2024-06-13 15:20 ` [Bug c++/115476] [13/14/15 Regression] " pinskia at gcc dot gnu.org 2024-06-13 15:36 ` mpolacek at gcc dot gnu.org 2024-06-13 15:45 ` mpolacek at gcc dot gnu.org 2024-06-13 15:52 ` mital at mitalashok dot co.uk 2024-06-13 15:56 ` mital at mitalashok dot co.uk 2024-06-13 16:22 ` mpolacek at gcc dot gnu.org [this message] 2024-06-13 16:26 ` mpolacek at gcc dot gnu.org 2024-06-13 18:14 ` mital at mitalashok dot co.uk 2024-06-18 14:39 ` mpolacek at gcc dot gnu.org 2024-06-25 21:45 ` cvs-commit at gcc dot gnu.org 2024-06-25 21:46 ` [Bug c++/115476] [13/14 " mpolacek 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-115476-4-9hqkGyaZ3z@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: linkBe 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).