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/107453] New: New stdarg tests in r13-3549-g4fe34cdcc80ac2 fail
Date: Fri, 28 Oct 2022 21:39:42 +0000 [thread overview]
Message-ID: <bug-107453-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107453
Bug ID: 107453
Summary: New stdarg tests in r13-3549-g4fe34cdcc80ac2 fail
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:4fe34cdcc80ac225b80670eabc38ac5e31ce8a5a, r13-3549-g4fe34cdcc80ac2
FAIL: gcc.dg/c2x-stdarg-4.c execution test
FAIL: gcc.dg/torture/c2x-stdarg-split-1a.c -O0 execution test
FAIL: gcc.dg/torture/c2x-stdarg-split-1a.c -O1 execution test
FAIL: gcc.dg/torture/c2x-stdarg-split-1a.c -O2 execution test
FAIL: gcc.dg/torture/c2x-stdarg-split-1a.c -O2 -flto -fno-use-linker-plugin
-flto-partition=none execution test
FAIL: gcc.dg/torture/c2x-stdarg-split-1a.c -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects execution test
FAIL: gcc.dg/torture/c2x-stdarg-split-1a.c -O3 -g execution test
FAIL: gcc.dg/torture/c2x-stdarg-split-1a.c -Os execution test
One traceback
(gdb) run
Starting program: /home/seurer/gcc/git/build/gcc-test/c2x-stdarg-4.exe
Program received signal SIGABRT, Aborted.
0x00002000002192a8 in raise () from /lib64/glibc-hwcaps/power9/libc-2.28.so
(gdb) where
#0 0x00002000002192a8 in raise () from /lib64/glibc-hwcaps/power9/libc-2.28.so
#1 0x00002000001f3eb4 in abort () from /lib64/glibc-hwcaps/power9/libc-2.28.so
#2 0x0000000010000fa0 in main () at
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/c2x-stdarg-4.c:153
The abort is from here:
if (f (1, 2.0, 3, 4.0) != 10.0)
abort ();
Author: Joseph Myers <joseph@codesourcery.com>
Date: Fri Oct 28 14:40:25 2022 +0000
c: tree: target: C2x (...) function prototypes and va_start relaxation
next reply other threads:[~2022-10-28 21:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 21:39 seurer at gcc dot gnu.org [this message]
2022-10-28 21:42 ` [Bug target/107453] " pinskia at gcc dot gnu.org
2022-10-31 17:08 ` ebotcazou at gcc dot gnu.org
2022-11-05 9:34 ` tschwinge at gcc dot gnu.org
2022-11-05 10:23 ` [Bug target/107453] [13 Regression] " rguenth at gcc dot gnu.org
2022-11-07 8:51 ` chenglulu at loongson dot cn
2023-01-06 14:00 ` jakub at gcc dot gnu.org
2023-01-09 12:37 ` cvs-commit at gcc dot gnu.org
2023-01-09 12:44 ` jakub at gcc dot gnu.org
2023-01-09 20:07 ` tschwinge at gcc dot gnu.org
2023-03-15 12:39 ` xry111 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-107453-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).