public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <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 10:30:19 +0000	[thread overview]
Message-ID: <bug-105469-4-GMfgKTp5No@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 #5 from Martin Liška <marxin at gcc dot gnu.org> ---
Reduced test-case:

namespace std {
template <class> struct char_traits;
template <typename _CharT, typename = char_traits<_CharT>> class basic_ostream;
struct ios_base {
  struct Init {
    Init();
  };
};
template <typename, typename> struct basic_ostream {
  void operator<<(const void *);
};
extern basic_ostream<char> cerr;
ios_base::Init __ioinit;
} // namespace std
enum Commit_Level { no_commit };
struct Writable {
  virtual void drop_fieldtimestampvalid_data() {}
  virtual void checkpoint(Commit_Level) {}
};
struct Posix_File {
  Posix_File();
  ~Posix_File();
};
Posix_File::Posix_File() {}
Posix_File::~Posix_File() {}
struct Readonly_Journal {
  Readonly_Journal();
  void play_until_checkpoint(Writable &writable) {
    writable.checkpoint(no_commit);
    std::cerr << "";
  }
};
Readonly_Journal::Readonly_Journal() {}
struct Writable_Journal : Readonly_Journal {
  Writable_Journal();
  ~Writable_Journal();
};
Writable_Journal::Writable_Journal() {}
Writable_Journal::~Writable_Journal() {}
struct Connection {
  virtual void push(Readonly_Journal &, long, bool) = 0;
};
template <typename Client_Data> struct Trans_NS_joedb_Client {
  Connection &connection;
  Client_Data data;
  Trans_NS_joedb_Client(Connection &, Posix_File file)
      : connection(connection), data(connection, file) {
    std::cerr << &data;
    data.update();
  }
};
struct Local_Connection : Connection {
  Posix_File file;
  void push(Readonly_Journal &, long, bool) {}
};
struct Generic_File_Database : Writable {
  Writable_Journal journal;
  Generic_File_Database();
  void checkpoint(Commit_Level) {}
};
struct Client_Data : Generic_File_Database {
  Client_Data(Connection &, Posix_File) {}
  void update() { journal.play_until_checkpoint(*this); }
};
struct Client : Trans_NS_joedb_Client<Client_Data> {
  Posix_File Client_local_file;
  Client() : Trans_NS_joedb_Client(connection, Client_local_file) {}
};
Generic_File_Database::Generic_File_Database() {}
struct Buggy_Client : Local_Connection, Client {};

int main() { Buggy_Client(); }

  parent reply	other threads:[~2022-05-04 10:30 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
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 [this message]
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-GMfgKTp5No@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).