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] New: FAIL: test-combination.c.exe test-functions.c.exe test-pr66779.c.exe test-threads.c.exe killed Date: Mon, 16 Nov 2020 23:11:23 +0000 [thread overview] Message-ID: <bug-97867-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97867 Bug ID: 97867 Summary: FAIL: test-combination.c.exe test-functions.c.exe test-pr66779.c.exe test-threads.c.exe killed Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: jit Assignee: dmalcolm at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- Today's build of mine of GCC trunk on x86_64-linux shows failures in the following tests: ! FAIL: test-combination.c.exe (1: +1) ! FAIL: test-functions.c.exe (1: +1) ! FAIL: test-pr66779.c.exe (1: +1) ! FAIL: test-threads.c.exe (1: +1) They all seem to fail with a SEGV: $ find gcc/testsuite -name "*.log" | xargs grep -e test-combination.c.exe -e test-functions.c.exe -e test-pr66779.c.exe -e test-threads.c.exe | grep FAIL) gcc/testsuite/jit/jit.log:FAIL: test-combination.c.exe killed: 23122 exp6 0 0 CHILDKILLED SIGSEGV {segmentation violation} gcc/testsuite/jit/jit.log:FAIL: test-functions.c.exe killed: 31302 exp6 0 0 CHILDKILLED SIGSEGV {segmentation violation} gcc/testsuite/jit/jit.log:FAIL: test-pr66779.c.exe killed: 28080 exp6 0 0 CHILDKILLED SIGSEGV {segmentation violation} gcc/testsuite/jit/jit.log:FAIL: test-threads.c.exe killed: 5980 exp6 0 0 CHILDKILLED SIGABRT SIGABRT
next reply other threads:[~2020-11-16 23:11 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-16 23:11 msebor at gcc dot gnu.org [this message] 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 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@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: linkBe 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).