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:17:36 +0000	[thread overview]
Message-ID: <bug-102766-4-Zltxs2BZEJ@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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |12.0
                 CC|                            |vries at gcc dot gnu.org
            Summary|[12 Regression] internal    |[12 Regression][nvptx]
                   |compiler error: in          |internal compiler error: in
                   |df_insn_delete, at          |df_insn_delete, at
                   |df-scan.c:949               |df-scan.c:949

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Bisecting shows that the ICE is exposed due to the var-tracking changes:

commit g:4cb52980e5d5fb64a393d385923da1b51ab34606
Author: Martin Liska <mliska@suse.cz>
Date:   Tue Oct 12 14:31:50 2021 +0200

    Eliminate AUTODETECT_VALUE usage in options.

    gcc/ChangeLog:

        * common.opt: Stop using AUTODETECT_VALUE
        and use EnabledBy where possible.
        * opts.c: Enable OPT_fvar_tracking with optimize >= 1.
        * toplev.c (AUTODETECT_VALUE): Remove macro.
        (process_options): Simplify by using EnabledBy and
        OPT_fvar_tracking.  Use OPTION_SET_P macro instead of
        AUTODETECT_VALUE.

  reply	other threads:[~2021-10-15  9:17 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 ` burnus at gcc dot gnu.org [this message]
2021-10-15  9:22 ` [Bug bootstrap/102766] [12 Regression][nvptx] " marxin at gcc dot gnu.org
2021-10-15  9:39 ` burnus at gcc dot gnu.org
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-Zltxs2BZEJ@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).