public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/107338] New: new test case gcc.dg/vect/vect-bitfield-read-7.c in r13-3413-ge10ca9544632db fails
Date: Thu, 20 Oct 2022 21:58:30 +0000 [thread overview]
Message-ID: <bug-107338-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107338
Bug ID: 107338
Summary: new test case gcc.dg/vect/vect-bitfield-read-7.c in
r13-3413-ge10ca9544632db fails
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:e10ca9544632dbff4759b4b92886cd96d0b9bdfe, r13-3413-ge10ca9544632db
make -k check-gcc RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-bitfield-read-7.c"
FAIL: gcc.dg/vect/vect-bitfield-read-7.c execution test
FAIL: gcc.dg/vect/vect-bitfield-read-7.c -flto -ffat-lto-objects execution test
# of expected passes 4
# of unexpected failures 2
I am only seeing this on BE systems (both power 7 and 8) and it fails the same
way for both 32 and 64 bits. There are no failure messages on the execution.
I tried a debug compilation but the traceback is not helpful:
seurer@makalu-lp1:~/gcc/git/build/gcc-test$
/home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/vect/vect-bitfield-read-7.c
-m64 -fdiagnostics-plain-output -flto -ffat-lto-objects -maltivec
-mpower8-vector -ftree-vectorize -fno-tree-loop-distribute-patterns
-fno-vect-cost-model -fno-common -O2 -g3 -fdump-tree-vect-details -lm -o
./vect-bitfield-read-7.exe
seurer@makalu-lp1:~/gcc/git/build/gcc-test$ gdb ./vect-bitfield-read-7.exe
(gdb) run
Starting program:
/home/seurer/gcc/git/build/gcc-test/./vect-bitfield-read-7.exe
Program received signal SIGABRT, Aborted.
0x00003fffb7cd268c in __GI_raise (sig=<optimized out>) at
../nptl/sysdeps/unix/sysv/linux/raise.c:55
55 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) where
#0 0x00003fffb7cd268c in __GI_raise (sig=<optimized out>) at
../nptl/sysdeps/unix/sysv/linux/raise.c:55
#1 0x00003fffb7cd4878 in __GI_abort () at abort.c:90
#2 0x0000000010000600 in .main ()
There's only one abort in the test case on line 37:
if (f(&A[0], N) != RES)
abort ();
commit e10ca9544632dbff4759b4b92886cd96d0b9bdfe
Author: Andre Vieira <andre.simoesdiasvieira@arm.com>
Date: Thu Oct 20 15:54:39 2022 +0100
vect: Fix vectype when widening container type in bitfield pattern
[PR107326]
next reply other threads:[~2022-10-20 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 21:58 seurer at gcc dot gnu.org [this message]
2022-10-20 22:05 ` [Bug other/107338] " pinskia at gcc dot gnu.org
2022-10-21 9:42 ` [Bug testsuite/107338] " linkw at gcc dot gnu.org
2022-10-21 10:59 ` avieira at gcc dot gnu.org
2022-10-21 13:04 ` linkw at gcc dot gnu.org
2022-10-25 5:20 ` cvs-commit at gcc dot gnu.org
2022-10-25 5:29 ` [Bug tree-optimization/107338] " linkw 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-107338-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: 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).