public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/104564] '-fcompare-debug' failure w/ -std=c++20 -O1 -fharden-conditional-branches -fopenacc -gno-statement-frontiers
Date: Thu, 24 Mar 2022 13:10:22 +0000	[thread overview]
Message-ID: <bug-104564-4-jGat9YD5k4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104564-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104564

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Alexandre Oliva <aoliva@gcc.gnu.org>:

https://gcc.gnu.org/g:fb488cba571539b6644e8f99f1dd997cdb4c82c1

commit r12-7801-gfb488cba571539b6644e8f99f1dd997cdb4c82c1
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Mar 24 10:02:29 2022 -0300

    hardened conditionals: drop copied identifiers

    The copies of identifiers, indended to associate hardening SSA
    temporaries to the original variables they refer to, end up causing
    -fcompare-debug to fail, because DECL_UIDs are not identical, and the
    nouid flag used in compare-debug dumps doesn't affect the uids in
    naked identifiers, so the divergence becomes apparent.

    This patch drops the naked identifiers.  Though somewhat desirable,
    they're not necessary.


    for  gcc/ChangeLog

            PR debug/104564
            * gimple-harden-conditionals.cc (detach_value): Keep temps
            anonymous.

    for  gcc/testsuite/ChangeLog

            PR debug/104564
            * c-c++-common/torture/harden-comp.c: Adjust.
            * c-c++-common/torture/harden-cond.c: Adjust.

  parent reply	other threads:[~2022-03-24 13:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 11:15 [Bug debug/104564] New: " asolokha at gmx dot com
2022-02-16 11:17 ` [Bug debug/104564] " asolokha at gmx dot com
2022-03-24  2:46 ` aoliva at gcc dot gnu.org
2022-03-24 13:10 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-24 13:19 ` aoliva 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-104564-4-jGat9YD5k4@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).