public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/102766] [12 Regression][nvptx] internal compiler error: in df_insn_delete, at df-scan.c:949
Date: Fri, 15 Oct 2021 09:39:32 +0000 [thread overview]
Message-ID: <bug-102766-4-cKTnqKfIPF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102766-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102766
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
... However, there is no effect when using
-f(no-)var-tracking(-uninit),
it has still an ICE in all cases.
(Well, except that -fvar-tracking-uninit shows the following before the ICE:
cc1: error: variable tracking requested, but not supported by this debug format
[-Werror])
* * *
And I observe that the following option is now set:
1511 if (!OPTION_SET_P (flag_var_tracking_uninit))
1512 flag_var_tracking_uninit = flag_var_tracking;
While the code before is entered and explicitly sets it to 0:
(gdb) p debug_hooks->var_location == do_nothing_debug_hooks.var_location
$5 = true
1481 /* We know which debug output will be used so we can set
flag_var_tracking
1482 and flag_var_tracking_uninit if the user has not specified them.
*/
1483 if (debug_info_level < DINFO_LEVEL_NORMAL
1484 || !dwarf_debuginfo_p ()
1485 || debug_hooks->var_location ==
do_nothing_debug_hooks.var_location)
1486 {
1487 if ((OPTION_SET_P (flag_var_tracking) && flag_var_tracking == 1)
1488 || (OPTION_SET_P (flag_var_tracking_uninit)
1489 && flag_var_tracking_uninit == 1))
1490 {
1491 if (debug_info_level < DINFO_LEVEL_NORMAL)
1492 warning_at (UNKNOWN_LOCATION, 0,
1493 "variable tracking requested, but useless
unless "
1494 "producing debug info");
1495 else
1496 warning_at (UNKNOWN_LOCATION, 0,
1497 "variable tracking requested, but not supported
"
1498 "by this debug format");
1499 }
1500 flag_var_tracking = 0;
1501 flag_var_tracking_uninit = 0;
1502 }
next prev parent reply other threads:[~2021-10-15 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 8:31 [Bug bootstrap/102766] New: [12 Regression] " burnus at gcc dot gnu.org
2021-10-15 9:17 ` [Bug bootstrap/102766] [12 Regression][nvptx] " burnus at gcc dot gnu.org
2021-10-15 9:22 ` marxin at gcc dot gnu.org
2021-10-15 9:39 ` burnus at gcc dot gnu.org [this message]
2021-10-15 9:45 ` marxin at gcc dot gnu.org
2021-10-15 10:32 ` marxin at gcc dot gnu.org
2021-10-15 10:43 ` burnus at gcc dot gnu.org
2021-10-21 12:31 ` [Bug middle-end/102766] " burnus at gcc dot gnu.org
2021-10-21 13:20 ` cvs-commit at gcc dot gnu.org
2021-10-21 13:21 ` 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-102766-4-cKTnqKfIPF@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).