public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/98294] New: [9/10/11 Regression] ICE in calculate_line_spans, at diagnostic-show-locus.c:1296 Date: Tue, 15 Dec 2020 17:20:03 +0000 [thread overview] Message-ID: <bug-98294-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98294 Bug ID: 98294 Summary: [9/10/11 Regression] ICE in calculate_line_spans, at diagnostic-show-locus.c:1296 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Old stuff, affects versions down to r6 : $ cat z1.c void f () { #line 9223372036854775807 g () + 1; } $ gcc-11-20201213 -c z1.c -Wall z1.c: In function 'f': z1.c:3:9: warning: line number out of range 3 | #line 9223372036854775807 | ^~~~~~~~~~~~~~~~~~~ z1.c:-1:3: warning: implicit declaration of function 'g' [-Wimplicit-function-declaration] z1.c: warning: value computed is not used [-Wunused-value] z1.c: internal compiler error: in calculate_line_spans, at diagnostic-show-locus.c:1296 0x1532394 calculate_line_spans ../../gcc/diagnostic-show-locus.c:1296 0x1532394 layout ../../gcc/diagnostic-show-locus.c:1003 0x1532572 diagnostic_show_locus(diagnostic_context*, rich_location*, diagnostic_t) ../../gcc/diagnostic-show-locus.c:2601 0x6e2435 c_diagnostic_finalizer ../../gcc/c-family/c-opts.c:174 0x152d744 diagnostic_report_diagnostic(diagnostic_context*, diagnostic_info*) ../../gcc/diagnostic.c:1223 0x152de6e diagnostic_impl ../../gcc/diagnostic.c:1366 0x152e392 warning_at(unsigned int, int, char const*, ...) ../../gcc/diagnostic.c:1503 0x64ea89 c_process_expr_stmt(unsigned int, tree_node*) ../../gcc/c/c-typeck.c:11213 0x64eb8d c_finish_expr_stmt(unsigned int, tree_node*) ../../gcc/c/c-typeck.c:11243 0x689d18 c_parser_statement_after_labels ../../gcc/c/c-parser.c:6249 0x68bd0a c_parser_compound_statement_nostart ../../gcc/c/c-parser.c:5788 0x68c583 c_parser_compound_statement ../../gcc/c/c-parser.c:5597 0x68de38 c_parser_declaration_or_fndef ../../gcc/c/c-parser.c:2539 0x694ca7 c_parser_external_declaration ../../gcc/c/c-parser.c:1777 0x6957c9 c_parser_translation_unit ../../gcc/c/c-parser.c:1650 0x6957c9 c_parse_file() ../../gcc/c/c-parser.c:21929 0x6e5532 c_common_parse_file() ../../gcc/c-family/c-opts.c:1211
next reply other threads:[~2020-12-15 17:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-15 17:20 gscfq@t-online.de [this message] 2020-12-16 8:21 ` [Bug c/98294] [9/10/11 Regression] ICE in calculate_line_spans, at diagnostic-show-locus.c:1296 since r6-6901-g876217ae71cf0b34 marxin at gcc dot gnu.org 2021-01-04 15:15 ` rguenth at gcc dot gnu.org 2021-01-14 11:07 ` rguenth at gcc dot gnu.org 2021-01-28 9:39 ` jakub at gcc dot gnu.org 2021-01-28 14:20 ` dmalcolm at gcc dot gnu.org 2021-06-01 8:19 ` [Bug c/98294] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-05-27 9:44 ` [Bug c/98294] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:42 ` jakub at gcc dot gnu.org 2023-07-07 10:38 ` [Bug c/98294] [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-98294-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: linkBe 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).