public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/114628] ICE with _BitInt returns_twice (and computed gotos) with -g and optimization
Date: Mon, 08 Apr 2024 14:13:40 +0000 [thread overview]
Message-ID: <bug-114628-4-J9jpIaUnPL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114628-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114628
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> Note we get 2 difference ICEs depending on if `#if ` is 1 or 0.
> It seems like it would be useful if some more torture tests for _BitInt were
> included so `-g` gets a little more testing.
We have lots of bitint torture tests, but because those tests often are fairly
expensive, they are usually excluded unless GCC_TEST_RUN_EXPENSIVE=1 (which I'm
quite often using for
make check-gcc -j32 -k GCC_TEST_RUN_EXPENSIVE=1
RUNTESTFLAGS="GCC_TEST_RUN_EXPENSIVE=1 dg.exp='*bitint* pr112673.c
builtin-stdc-bit-*.c pr112566-2.c pr112511.c' dg-torture.exp=*bitint*
dfp.exp=*bitint*"
testing on x86_64/i686-linux.
next prev parent reply other threads:[~2024-04-08 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 10:53 [Bug middle-end/114628] New: [14 Regression] ICE in gimple_check_failed at gimple.cc:1337 while compiling bitint-100.c pheeck at gcc dot gnu.org
2024-04-07 10:54 ` [Bug middle-end/114628] " pheeck at gcc dot gnu.org
2024-04-07 20:18 ` [Bug middle-end/114628] ICE with _BitInt with computed gotos with returns_twice and -g and optimization pinskia at gcc dot gnu.org
2024-04-08 14:11 ` [Bug middle-end/114628] ICE with _BitInt returns_twice (and computed gotos) with " jakub at gcc dot gnu.org
2024-04-08 14:13 ` jakub at gcc dot gnu.org [this message]
2024-04-09 7:29 ` cvs-commit at gcc dot gnu.org
2024-04-09 7:30 ` jakub 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-114628-4-J9jpIaUnPL@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).