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/104586] New: New test case gcc.dg/pr102798.c in 523f5950c70d65714bedf9d5fe164d9e6d69dd87 fails
Date: Thu, 17 Feb 2022 21:13:18 +0000 [thread overview]
Message-ID: <bug-104586-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104586
Bug ID: 104586
Summary: New test case gcc.dg/pr102798.c in
523f5950c70d65714bedf9d5fe164d9e6d69dd87 fails
Product: gcc
Version: 12.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:523f5950c70d65714bedf9d5fe164d9e6d69dd87
make -k check-gcc RUNTESTFLAGS="dg.exp=gcc.dg/pr102798.c"
FAIL: gcc.dg/pr102798.c execution test
# of expected passes 1
# of unexpected failures 1
Program received signal SIGSEGV, Segmentation fault.
BUF_reverse (out=<optimized out>, out@entry=0x7ffffffff360 "", in=<optimized
out>, in@entry=0x0, size=size@entry=40) at
/home/seurer/gcc/git/gcc-9/gcc/testsuite/gcc.dg/pr102798.c:14
14 *out++ = *in++;
(gdb) where
#0 BUF_reverse (out=<optimized out>, out@entry=0x7ffffffff360 "",
in=<optimized out>, in@entry=0x0, size=size@entry=40) at
/home/seurer/gcc/git/gcc-9/gcc/testsuite/gcc.dg/pr102798.c:14
#1 0x0000000010000564 in main () at
/home/seurer/gcc/git/gcc-9/gcc/testsuite/gcc.dg/pr102798.c:35
commit 523f5950c70d65714bedf9d5fe164d9e6d69dd87 (HEAD, origin/releases/gcc-9)
Author: Richard Biener <rguenther@suse.de>
Date: Mon Oct 18 09:10:43 2021 +0200
tree-optimization/102798 - avoid copying PTA info to old SSA names
next reply other threads:[~2022-02-17 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 21:13 seurer at gcc dot gnu.org [this message]
2022-02-18 6:58 ` [Bug other/104586] " rguenth at gcc dot gnu.org
2022-02-18 7:10 ` rguenth at gcc dot gnu.org
2022-02-18 7:10 ` rguenth 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-104586-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).