public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/106568] -freorder-blocks-algorithm appears to causes a crash in stable code, no way to disable it
Date: Tue, 06 Feb 2024 20:20:05 +0000	[thread overview]
Message-ID: <bug-106568-4-jc2jtmQAex@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106568-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568

--- Comment #22 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Created attachment 57344
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57344&action=edit
Gzipped preprocessed source

With -O2 -fsantiize=unreachable this prints an error:

pubkey.h:2209:32: runtime error: execution reached an unreachable program point

That happens from the constructor at validat9.cpp:455 

#0 
CryptoPP::PK_FinalTemplate<CryptoPP::DL_VerifierImpl<CryptoPP::DL_SignatureSchemeOptions<CryptoPP::DL_SS<CryptoPP::DL_Keys_ECGDSA<CryptoPP::ECP>,
CryptoPP::DL_Algorithm_ECGDSA<CryptoPP::ECP>,
CryptoPP::DL_SignatureMessageEncodingMethod_DSA, CryptoPP::SHA1, int>,
CryptoPP::DL_Keys_ECGDSA<CryptoPP::ECP>,
CryptoPP::DL_Algorithm_ECGDSA<CryptoPP::ECP>,
CryptoPP::DL_SignatureMessageEncodingMethod_DSA, CryptoPP::SHA1> >
>::PK_FinalTemplate (algorithm=..., this=0x7fffffffc7d0) at
/tmp/cryptopp/cryptlib.h:2626
#1  CryptoPP::Test::ValidateECGDSA (thorough=thorough@entry=true) at
validat9.cpp:455
#2  0x000000000043448f in CryptoPP::Test::Validate (alg=<optimized out>,
thorough=thorough@entry=true) at test.cpp:995
#3  0x000000000043a303 in CryptoPP::Test::scoped_main (argc=3,
argv=0x7fffffffd6b8) at test.cpp:401
#4  0x000000000043aaf3 in main (argc=<optimized out>, argv=<optimized out>) at
test.cpp:1094


I don't see anything obviously wrong with the code.

  parent reply	other threads:[~2024-02-06 20:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 21:20 [Bug c++/106568] New: " noloader at gmail dot com
2022-08-08 21:30 ` [Bug middle-end/106568] " ktkachov at gcc dot gnu.org
2022-08-08 21:34 ` pinskia at gcc dot gnu.org
2022-08-08 21:36 ` [Bug rtl-optimization/106568] " pinskia at gcc dot gnu.org
2022-08-08 21:40 ` pinskia at gcc dot gnu.org
2022-08-08 21:52 ` noloader at gmail dot com
2022-08-08 22:00 ` pinskia at gcc dot gnu.org
2022-08-08 22:18 ` noloader at gmail dot com
2022-08-08 22:25 ` pinskia at gcc dot gnu.org
2022-08-08 23:05 ` noloader at gmail dot com
2022-08-08 23:20 ` noloader at gmail dot com
2022-08-08 23:22 ` pinskia at gcc dot gnu.org
2022-08-08 23:23 ` pinskia at gcc dot gnu.org
2022-08-09  0:56 ` noloader at gmail dot com
2022-08-09  1:09 ` noloader at gmail dot com
2022-08-09  1:35 ` noloader at gmail dot com
2022-08-09  1:45 ` pinskia at gcc dot gnu.org
2022-08-09  1:46 ` pinskia at gcc dot gnu.org
2022-08-09  2:05 ` noloader at gmail dot com
2022-08-09  4:22 ` noloader at gmail dot com
2022-08-09  4:22 ` noloader at gmail dot com
2022-08-09  7:57 ` rguenth at gcc dot gnu.org
2024-02-06 20:20 ` redi at gcc dot gnu.org [this message]
2024-02-06 20:28 ` pinskia at gcc dot gnu.org
2024-02-06 21:50 ` pinskia at gcc dot gnu.org
2024-02-06 22:21 ` [Bug ipa/106568] " pinskia 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-106568-4-jc2jtmQAex@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).