public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bruce at hoult dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114194] ICE when using std::unique_ptr with xtheadvector Date: Tue, 05 Mar 2024 02:21:57 +0000 [thread overview] Message-ID: <bug-114194-4-UhgC1Gz3kF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114194-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114194 --- Comment #6 from Bruce Hoult <bruce at hoult dot org> --- The ICE also happens with bzero(). The ICE does NOT happen with a constant length of 16 of greater, in which case a function call is made instead of expanding inline. With rv64gv or rv64gcv a series of N `sb` are generated (N < 16) With rv64gc_xtheadvector, N >= 6, and -Os a tail call to memset is generated, no ICE. With N < 6 ... ICE. So the problem is only trying to expand memset() or bzero() inline. Does it try to use a vectorised memset? That doesn't happen with rv64gcv. memcpy() does not ICE for any N. I assume the originally reported C++ code is generating a memset() to initialise one of the classes/structs.
next prev parent reply other threads:[~2024-03-05 2:21 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-01 17:02 [Bug target/114194] New: " camel-cdr at protonmail dot com 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 [this message] 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-UhgC1Gz3kF@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).