public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/106208] [12/13 Regression] ICE in branch_prob, at profile.cc:1459 since r12-5275-gbcebd05720540e25 Date: Mon, 25 Jul 2022 15:13:12 +0000 [thread overview] Message-ID: <bug-106208-4-ed2cRcwl8w@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106208-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106208 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|fortran |middle-end Priority|P3 |P2 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- #1 0x0000000001423960 in branch_prob (thunk=false) at /home/rguenther/src/trunk/gcc/profile.cc:1459 1459 gcc_checking_assert (!RESERVED_LOCATION_P (loc)); (gdb) l 1454 gcov_position_t offset = 0; 1455 1456 if (bb == ENTRY_BLOCK_PTR_FOR_FN (cfun)->next_bb) 1457 { 1458 location_t loc = DECL_SOURCE_LOCATION (current_function_decl); 1459 gcc_checking_assert (!RESERVED_LOCATION_P (loc)); 1460 seen_locations.add (loc); 1461 expanded_location curr_location = expand_location (loc); 1462 output_location (&streamed_locations, curr_location.file, 1463 MAX (1, curr_location.line), &offset, bb); (gdb) p loc $1 = 0 (gdb) p current_function_decl $2 = <function_decl 0x7ffff6317d00 _caf_init.0> (gdb) p $2->decl_common.artificial_flag $3 = 0 I was to say that for artificial functions a reserved location could be expected. But _caf_init.0 isn't even artificial (which is probably a bug). In the non-entry block case we do if (!RESERVED_LOCATION_P (loc)) { seen_locations.add (loc); which seems an obvious thing to do here as well. But it's really Thomas who should comment since he put in the assert (uncovering a previous issue). Not really a frontend bug (if it were DECL_ARTIFICIAL the ICE would occur anyway).
next prev parent reply other threads:[~2022-07-25 15:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-05 18:48 [Bug fortran/106208] New: [12/13 Regression] ICE in branch_prob, at profile.cc:1459 gscfq@t-online.de 2022-07-07 8:08 ` [Bug fortran/106208] " rguenth at gcc dot gnu.org 2022-07-07 12:55 ` [Bug fortran/106208] [12/13 Regression] ICE in branch_prob, at profile.cc:1459 since r12-5275-gbcebd05720540e25 marxin at gcc dot gnu.org 2022-07-25 15:13 ` rguenth at gcc dot gnu.org [this message] 2022-07-25 15:42 ` [Bug middle-end/106208] " tschwinge at gcc dot gnu.org 2022-10-25 10:52 ` tschwinge at gcc dot gnu.org 2023-05-08 12:25 ` [Bug middle-end/106208] [12/13/14 " rguenth at gcc dot gnu.org 2024-03-11 4:41 ` [Bug middle-end/106208] [12 " 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-106208-4-ed2cRcwl8w@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).