public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109318] csmith: -fipa-cp seems to cause trouble
Date: Tue, 28 Mar 2023 17:39:45 +0000 [thread overview]
Message-ID: <bug-109318-4-Kp5lz5824V@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109318-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109318
--- Comment #1 from David Binderman <dcb314 at hotmail dot com> ---
In gdb:
gdb) r 1
Starting program: /home/dcb36/csmith/a.out 1
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x0000000000401630 in func_14 (p_15=-3035) at runData/keep/in.46087.c:217
217 (*l_1508) = func_16(l_22[0][6],
(safe_add_func_uint64_t_u_u((~((safe_div_func_uint64_t_u_u(func_28(&g_7,
g_12.f0, func_32(l_34[0][1])), ((l_1506[6] != (+(p_15 || l_1506[6]))) ||
p_15))) < 0xCFA7L)), p_15)), l_1508, l_1509, p_15);
Missing separate debuginfos, use: dnf debuginfo-install
glibc-2.35-20.fc36.x86_64
(gdb) bt
#0 0x0000000000401630 in func_14 (p_15=-3035) at runData/keep/in.46087.c:217
#1 func_1 () at runData/keep/in.46087.c:177
#2 main (argc=<optimized out>, argv=<optimized out>)
at runData/keep/in.46087.c:764
(gdb)
next prev parent reply other threads:[~2023-03-28 17:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 16:54 [Bug c/109318] New: " dcb314 at hotmail dot com
2023-03-28 17:39 ` dcb314 at hotmail dot com [this message]
2023-03-28 18:37 ` [Bug tree-optimization/109318] " dcb314 at hotmail dot com
2023-03-28 19:15 ` dcb314 at hotmail dot com
2023-03-28 22:15 ` dcb314 at hotmail dot com
2023-03-29 7:46 ` [Bug ipa/109318] csmith: -fipa-cp seems to cause trouble since r12-2523-g13586172d0b70c marxin at gcc dot gnu.org
2023-03-29 8:10 ` [Bug ipa/109318] [12/13 Regression] " marxin at gcc dot gnu.org
2023-03-29 8:13 ` rguenth at gcc dot gnu.org
2023-03-29 8:32 ` rguenth at gcc dot gnu.org
2023-03-29 8:37 ` jamborm at gcc dot gnu.org
2023-03-31 11:18 ` jamborm at gcc dot gnu.org
2023-04-06 17:01 ` jamborm at gcc dot gnu.org
2023-04-17 11:06 ` cvs-commit at gcc dot gnu.org
2023-04-17 14:16 ` [Bug ipa/109318] [12 " jamborm at gcc dot gnu.org
2023-04-26 16:45 ` cvs-commit at gcc dot gnu.org
2023-04-26 16:45 ` jamborm 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-109318-4-Kp5lz5824V@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).