public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yronglin777 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110175] New: [GCC][Crash] GCC Crash on valid code
Date: Thu, 08 Jun 2023 14:28:04 +0000	[thread overview]
Message-ID: <bug-110175-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110175
           Summary: [GCC][Crash] GCC Crash on valid code
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: yronglin777 at gmail dot com
  Target Milestone: ---

https://godbolt.org/z/Wf7M89v8x

```
template<class T> auto f(T t) -> decltype(++t) { return t; }
void f(...) {}
void g() { f(true); }
```

```
internal compiler error: error reporting routines re-entered.
0x23b8691 warning_at(unsigned int, int, char const*, ...)
        ???:0
0xd39208 cp_build_unary_op(tree_code, tree_node*, bool, int)
        ???:0
0xacd484 build_new_op(op_location_t const&, tree_code, int, tree_node*,
tree_node*, tree_node*, tree_node*, tree_node**, int)
        ???:0
0xd370e3 build_x_unary_op(unsigned int, tree_code, cp_expr, tree_node*, int)
        ???:0
0xcb685f tsubst(tree_node*, tree_node*, int, tree_node*)
        ???:0
0x23d8a2c pp_format(pretty_printer*, text_info*)
        ???:0
0x23d9c3d pp_format_verbatim(pretty_printer*, text_info*)
        ???:0
0x23d9d25 pp_verbatim(pretty_printer*, char const*, ...)
        ???:0
0x23b7895 diagnostic_report_diagnostic(diagnostic_context*, diagnostic_info*)
        ???:0
0x23b8691 warning_at(unsigned int, int, char const*, ...)
        ???:0
0xd45bf1 check_return_expr(tree_node*, bool*)
        ???:0
0xcef6a3 finish_return_stmt(tree_node*)
        ???:0
0xcaf2f8 instantiate_decl(tree_node*, bool, bool)
        ???:0
0xcda84b instantiate_pending_templates(int)
        ???:0
0xb8e905 c_parse_final_cleanups()
        ???:0
0xdbe998 c_common_parse_file()
        ???:0
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
Compiler returned: 1
```

If remove the function body of 2 `f` functions, GCC will works well.
```
template<class T> auto f(T t) -> decltype(++t);
void f(...);
void g() { f(true); }
```

             reply	other threads:[~2023-06-08 14:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 14:28 yronglin777 at gmail dot com [this message]
2023-06-08 18:05 ` [Bug c++/110175] " mpolacek at gcc dot gnu.org
2023-06-09  4:13 ` yronglin777 at gmail dot com
2023-06-28 15:52 ` cvs-commit at gcc dot gnu.org
2023-06-28 15:52 ` mpolacek at gcc dot gnu.org
2023-06-28 18:52 ` ppalka 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-110175-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: 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).