public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "remi.coulom at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/105469] "execution reached an unreachable program point" with -flto
Date: Wed, 04 May 2022 07:15:10 +0000 [thread overview]
Message-ID: <bug-105469-4-1mDPp1A4cY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105469-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105469
--- Comment #2 from Rémi Coulom <remi.coulom at gmail dot com> ---
(In reply to Richard Biener from comment #1)
> I can reproduce what you observe with -O3 -fwhole-program
> -fsanitize=unreachable
> (without the sanitize it gets into an infinite loop). -fno-ipa-cp-clone
> avoids
> the issue (whatever it is exactly).
>
> Can you attach un-preprocessed source as well? You seem to be not using any
> non-standard header files.
Thanks for checking my code.
The code is available on github:
https://github.com/Remi-Coulom/joedb
Necessary files to replicate the bug can be found there:
https://github.com/Remi-Coulom/joedb/tree/master/doc/source/tutorial/gcc_bug
repro.cpp and all_includes.h should be enough.
I produced repro.cpp by preprocessing bug.cpp and pruning a lot of code. I
suppose repro.cpp should be enough for your purpose. If you ever wish to
compile bug.cpp you'll have to compile joedb first by running "./generate.sh"
in doc/source/tutorial.
next prev parent reply other threads:[~2022-05-04 7:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 19:58 [Bug c++/105469] New: " remi.coulom at gmail dot com
2022-05-04 6:28 ` [Bug middle-end/105469] " rguenth at gcc dot gnu.org
2022-05-04 7:15 ` remi.coulom at gmail dot com [this message]
2022-05-04 8:54 ` marxin at gcc dot gnu.org
2022-05-04 9:28 ` jakub at gcc dot gnu.org
2022-05-04 10:30 ` marxin at gcc dot gnu.org
2022-05-04 10:33 ` marxin at gcc dot gnu.org
2022-05-04 10:34 ` marxin at gcc dot gnu.org
2022-05-04 10:44 ` rguenth at gcc dot gnu.org
2022-05-04 10:50 ` marxin at gcc dot gnu.org
2022-05-04 10:53 ` marxin at gcc dot gnu.org
2022-05-04 11:01 ` [Bug middle-end/105469] "execution reached an unreachable program point" with -flto since r5-7027-g0b986c6ac777aa4e marxin at gcc dot gnu.org
2022-05-04 11:01 ` jakub at gcc dot gnu.org
2022-05-05 4:50 ` pinskia at gcc dot gnu.org
2022-05-11 12:47 ` remi.coulom at gmail dot com
2022-09-14 13:08 ` [Bug middle-end/105469] [10/11/12/13 Regression] " rguenth at gcc dot gnu.org
2023-01-18 16:46 ` jakub at gcc dot gnu.org
2023-01-18 16:47 ` jakub at gcc dot gnu.org
2023-01-18 21:30 ` hubicka at gcc dot gnu.org
2023-01-19 13:25 ` jamborm at gcc dot gnu.org
2023-07-07 10:43 ` [Bug middle-end/105469] [11/12/13/14 " 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-105469-4-1mDPp1A4cY@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).