public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/115575] New: experimental/simd/pr115454_find_last_set.cc FAILs Date: Fri, 21 Jun 2024 07:39:07 +0000 [thread overview] Message-ID: <bug-115575-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115575 Bug ID: 115575 Summary: experimental/simd/pr115454_find_last_set.cc FAILs Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: mkretz at gcc dot gnu.org Target Milestone: --- Target: sparc-sun-solaris2.11 The new experimental/simd/pr115454_find_last_set.cc test FAILs on 32 and 64-bit Solaris/SPARC: FAIL: experimental/simd/pr115454_find_last_set.cc -mcpu=ultrasparc -mvis -O2 -Wno-psabi execution test This happens even when compiling with -g3 -O0. The test aborts: Thread 2 received signal SIGABRT, Aborted. [Switching to Thread 1 (LWP 1)] 0xfea79e4c in __lwp_sigqueue () from /lib/libc.so.1 (gdb) bt #0 0xfea79e4c in __lwp_sigqueue () from /lib/libc.so.1 #1 0xfe9b75d8 in raise () from /lib/libc.so.1 #2 0xfe988840 in abort () from /lib/libc.so.1 #3 0x000132e4 in main () at /vol/gcc/src/hg/master/local/libstdc++-v3/testsuite/experimental/simd/pr115454_find_last_set.cc:48 r2 = 7 at this point.
next reply other threads:[~2024-06-21 7:39 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-21 7:39 ro at gcc dot gnu.org [this message] 2024-06-21 7:39 ` [Bug libstdc++/115575] " ro at gcc dot gnu.org 2024-06-21 9:24 ` redi at gcc dot gnu.org 2024-06-21 9:59 ` mkretz at gcc dot gnu.org 2024-06-21 10:18 ` mkretz at gcc dot gnu.org 2024-06-21 10:49 ` mkretz at gcc dot gnu.org 2024-06-21 11:07 ` mkretz at gcc dot gnu.org 2024-06-21 16:06 ` cvs-commit at gcc dot gnu.org 2024-06-21 16:07 ` cvs-commit at gcc dot gnu.org 2024-06-21 16:20 ` cvs-commit at gcc dot gnu.org 2024-06-21 16:26 ` cvs-commit at gcc dot gnu.org 2024-06-21 16:26 ` cvs-commit 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-115575-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).