public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/107193] [13 regression] bootstrap error caused by r13-3172-gf30e9fd33e56a5 Date: Mon, 10 Oct 2022 08:29:41 +0000 [thread overview] Message-ID: <bug-107193-4-MOTZzn5nBG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107193-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107193 --- Comment #3 from Hongtao.liu <crazylht at gmail dot com> --- 1212 /* Traverse the basic block, if two function calls within a basic block 1213 are mapped to the same line, assign a new discriminator because a call 1214 stmt could be a split point of a basic block. */ 1215 for (gsi = gsi_start_bb (bb); !gsi_end_p (gsi); gsi_next (&gsi)) 1216 { 1217 gimple *stmt = gsi_stmt (gsi); 1218 expanded_location curr_locus_e; Shouldn't curr_locus_e be defined outside of the loop? orelse, the second iteration, it will be uninitialized and pased to same_line_p? 1219 if (curr_locus == UNKNOWN_LOCATION) 1220 { 1221 curr_locus = gimple_location (stmt); 1222 curr_locus_e = expand_location (curr_locus); 1223 } 1224 else if (!same_line_p (curr_locus, &curr_locus_e, gimple_location (stmt))) 1225 { 1226 curr_locus = gimple_location (stmt); 1227 curr_locus_e = expand_location (curr_locus); 1228 curr_discr = 0; 1229 } 1230 else if (curr_discr != 0) 1231 { 1232 location_t loc = gimple_location (stmt); 1233 location_t dloc = location_with_discriminator (loc, curr_discr); 1234 gimple_set_location (stmt, dloc); 1235 } 1236 /* Allocate a new discriminator for CALL stmt. */ 1237 if (gimple_code (stmt) == GIMPLE_CALL) 1238 curr_discr = next_discriminator_for_locus (curr_locus); 1239 }
next prev parent reply other threads:[~2022-10-10 8:29 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-09 11:37 [Bug bootstrap/107193] New: " crazylht at gmail dot com 2022-10-09 18:52 ` [Bug bootstrap/107193] " pinskia at gcc dot gnu.org 2022-10-09 18:52 ` [Bug debug/107193] " pinskia at gcc dot gnu.org 2022-10-10 7:22 ` rguenth at gcc dot gnu.org 2022-10-10 7:28 ` crazylht at gmail dot com 2022-10-10 8:18 ` crazylht at gmail dot com 2022-10-10 8:29 ` crazylht at gmail dot com [this message] 2022-10-10 13:28 ` marxin at gcc dot gnu.org 2022-10-10 20:49 ` erozen at microsoft dot com 2022-10-10 22:42 ` hjl.tools at gmail dot com 2022-10-10 22:45 ` hjl.tools at gmail dot com 2022-10-10 23:00 ` erozen at microsoft dot com 2022-10-11 2:51 ` erozen at microsoft dot com 2022-10-11 6:35 ` cvs-commit at gcc dot gnu.org 2022-10-11 7:11 ` marxin 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-107193-4-MOTZzn5nBG@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).