public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "camel-cdr at protonmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114194] New: ICE when using std::unique_ptr with xtheadvector Date: Fri, 01 Mar 2024 17:02:43 +0000 [thread overview] Message-ID: <bug-114194-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114194 Bug ID: 114194 Summary: ICE when using std::unique_ptr with xtheadvector Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: camel-cdr at protonmail dot com Target Milestone: --- Using std::unique_ptr with xtheadvector enabled causes an ICE: #include <memory> extern void use(std::unique_ptr<int> &x); void test(size_t n) { std::unique_ptr<int> x; use(x); } See also: https://godbolt.org/z/6nbhxKdfd I've managed to reduce the problem to the following set of templates, but I have no idea how this could cause the ICE. struct S1 { int x; }; struct S2 { constexpr S2() { } template<class T> S2(T&); }; struct S3 : S1, S2 { constexpr S3() : S1() { } S3(S3&); }; void f(S3 &) { S3 x; f(x); } See also: https://godbolt.org/z/5YxM6jd3s It's extremely brittle, the ICE goes away, if you remove constexpr, the reference, or any other part I could think of.
next reply other threads:[~2024-03-01 17:02 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-01 17:02 camel-cdr at protonmail dot com [this message] 2024-03-02 9:22 ` [Bug target/114194] " pinskia at gcc dot gnu.org 2024-03-04 14:14 ` pinskia at gcc dot gnu.org 2024-03-04 19:26 ` bruce at hoult dot org 2024-03-04 23:27 ` bruce at hoult dot org 2024-03-05 0:04 ` bruce at hoult dot org 2024-03-05 2:21 ` bruce at hoult dot org 2024-03-21 15:20 ` cmuellner at gcc dot gnu.org 2024-03-22 7:43 ` cmuellner 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-114194-4@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).