public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/104564] New: '-fcompare-debug' failure w/ -std=c++20 -O1 -fharden-conditional-branches -fopenacc -gno-statement-frontiers
Date: Wed, 16 Feb 2022 11:15:33 +0000	[thread overview]
Message-ID: <bug-104564-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104564
           Summary: '-fcompare-debug' failure w/ -std=c++20 -O1
                    -fharden-conditional-branches -fopenacc
                    -gno-statement-frontiers
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: compare-debug-failure
          Severity: normal
          Priority: P3
         Component: debug
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---
            Target: aarch64-linux-gnu

gcc 12.0.1 20220213 snapshot (g:58aeb75d4097010ad9bb72b964265b18ab284f93) fails
-fcompare-debug check when compiling the following testcase, partially reduced
from libstdc++-v3/testsuite/25_algorithms/inplace_merge/1.cc, w/ -std=c++20 -O1
-fharden-conditional-branches -fopenacc -gno-statement-frontiers:

#include <algorithm>
#include <testsuite_iterators.h>

typedef
  __gnu_test::test_container<int, __gnu_test::bidirectional_iterator_wrapper>
  container;

void test1() {
  int array[] = {};
  container con2(array, array);
  std::inplace_merge(con2.begin(), con2.begin(), con2.end());
}

% aarch64-linux-gnu-g++-12.0.1 -std=c++20 -O1 -fcompare-debug
-fharden-conditional-branches -fopenacc -gno-statement-frontiers -c bdxhor92.cc
aarch64-linux-gnu-g++-12.0.1: error: bdxhor92.cc: '-fcompare-debug' failure

It is very fragile, even adding -save-temps makes the failure disappear, so I
could not reduce it any further. If I get the dumps right, the difference
starts in einline.

             reply	other threads:[~2022-02-16 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 11:15 asolokha at gmx dot com [this message]
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
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@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).