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/105041] New: '-fcompare-debug' failure w/ -mcpu=power6 -O2 -fharden-compares -frename-registers
Date: Thu, 24 Mar 2022 07:38:46 +0000	[thread overview]
Message-ID: <bug-105041-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105041
           Summary: '-fcompare-debug' failure w/ -mcpu=power6 -O2
                    -fharden-compares -frename-registers
           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: powerpc-*-linux-gnu

Created attachment 52678
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52678&action=edit
gkd diff

gcc 12.0.1 20220320 snapshot (g:6f30c4cd38b8385d62358065d795df590e752d6e) fails
-fcompare-debug check when compiling the following testcase w/ -mcpu=power6 -O2
-fcompare-debug -fharden-compares -frename-registers:

double m;
int n;

unsigned int
foo (unsigned int x, int y)
{
  long long int a = y, b = !a;
  int c = 0;

  if (b != x)
    while ((int) m == a)
      {
        c = a;
        a = 0;
        x = 0;
      }

  n = b = y;

  return x + c;
}

% powerpc-e300c3-linux-gnu-gcc-12.0.1 -mcpu=power6 -O2 -fcompare-debug
-fharden-compares -frename-registers -c ck9whkva.c
powerpc-e300c3-linux-gnu-gcc-12.0.1: error: ck9whkva.c: '-fcompare-debug'
failure

gkd diff attached.

I suppose it is really a duplicate of PR104771.

             reply	other threads:[~2022-03-24  7:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24  7:38 asolokha at gmx dot com [this message]
2022-03-24  9:02 ` [Bug debug/105041] " rguenth at gcc dot gnu.org
2022-03-29 21:58 ` bergner at gcc dot gnu.org
2022-03-29 22:13 ` bergner at gcc dot gnu.org
2022-04-01 13:33 ` bergner at gcc dot gnu.org
2022-04-05 22:46 ` segher at gcc dot gnu.org
2022-04-07  5:30 ` jskumari at gcc dot gnu.org
2022-06-14 17:39 ` [Bug rtl-optimization/105041] " cvs-commit at gcc dot gnu.org
2022-06-15  5:25 ` jskumari at gcc dot gnu.org
2022-06-16  5:08 ` jskumari at gcc dot gnu.org
2022-07-14 14:07 ` cvs-commit at gcc dot gnu.org
2022-07-21  6:38 ` cvs-commit at gcc dot gnu.org
2022-07-22  9:53 ` cvs-commit at gcc dot gnu.org
2022-07-23  6:55 ` asolokha at gmx dot com
2022-07-23 16:28 ` bergner 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-105041-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).