public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/97867] FAIL: test-combination.c.exe test-functions.c.exe test-pr66779.c.exe test-threads.c.exe killed
Date: Tue, 24 Nov 2020 00:05:01 +0000 [thread overview]
Message-ID: <bug-97867-4-RTceRASXWp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97867-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97867
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
The backtrace from test-combination.c.exe shows the SEGV does happen in
thunk_info::release (). Ditto for test-functions.c.exe.
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5d74153 in free () from /lib64/libc.so.6
Missing separate debuginfos, use: dnf debuginfo-install gmp-6.1.2-9.fc29.x86_64
libmpc-1.1.0-2.fc29.x86_64 mpfr-3.1.6-2.fc29.x86_64
(gdb) bt
#0 0x00007ffff5d74153 in free () from /lib64/libc.so.6
#1 0x00007ffff654bd62 in thunk_info::release () at
/ssd/test/src/gcc/dump-type-attr/gcc/cgraph.c:4024
#2 cgraph_c_finalize () at /ssd/test/src/gcc/dump-type-attr/gcc/cgraph.c:4017
#3 0x00007ffff69b2229 in toplev::finalize (this=this@entry=0x7fffffffdd4e)
at /ssd/test/src/gcc/dump-type-attr/gcc/toplev.c:2508
#4 0x00007ffff64a31b0 in gcc::jit::playback::context::compile
(this=this@entry=0x7fffffffdde0)
at /ssd/test/src/gcc/dump-type-attr/gcc/jit/jit-playback.c:2124
#5 0x00007ffff6498bc6 in gcc::jit::recording::context::compile
(this=this@entry=0x47b3f0)
at /ssd/test/src/gcc/dump-type-attr/gcc/jit/jit-recording.c:1397
#6 0x00007ffff648a3bb in gcc_jit_context_compile (ctxt=0x47b3f0)
at /ssd/test/src/gcc/dump-type-attr/gcc/jit/libgccjit.c:2827
#7 0x000000000041be40 in test_jit (
argv0=0x7fffffffe2fe
"/ssd/test/build/gcc-gcc-dump-type-attr/gcc/testsuite/jit/test-combination.c.exe",
user_data=0x0) at
/ssd/test/src/gcc/dump-type-attr/gcc/testsuite/jit.dg/harness.h:371
#8 0x000000000041bf30 in main (argc=1, argv=0x7fffffffdfe8)
at /ssd/test/src/gcc/dump-type-attr/gcc/testsuite/jit.dg/harness.h:419
next prev parent reply other threads:[~2020-11-24 0:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 23:11 [Bug jit/97867] New: " msebor at gcc dot gnu.org
2020-11-16 23:16 ` [Bug jit/97867] " dmalcolm at gcc dot gnu.org
2020-11-24 0:05 ` msebor at gcc dot gnu.org [this message]
2020-11-24 18:27 ` [Bug jit/97867] [11 Regression] thunk_info::release breaks function calls in libgccjit dmalcolm at gcc dot gnu.org
2020-11-24 18:41 ` hubicka at gcc dot gnu.org
2020-11-29 22:22 ` cvs-commit at gcc dot gnu.org
2020-11-29 22:25 ` hubicka at gcc dot gnu.org
2020-11-30 14:09 ` dmalcolm at gcc dot gnu.org
2020-11-30 14:29 ` hubicka at ucw dot cz
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-97867-4-RTceRASXWp@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).