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/104771] New: '-fcompare-debug' failure w/ -mno-vsx -O1 -frename-registers
Date: Thu, 03 Mar 2022 12:56:46 +0000	[thread overview]
Message-ID: <bug-104771-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104771
           Summary: '-fcompare-debug' failure w/ -mno-vsx -O1
                    -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-e300c3-linux-gnu

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

g++ 12.0.1 20220227 snapshot (g:d1574a9b820f17adb9004255e2018967e9be063b) fails
-fcompare-debug check when compiling the following testcase w/ -mno-vsx -O1
-frename-registers:

int n;

void
quux ();

template <typename>
void
bar (long double y)
{
  for (int i = 0; i < n; ++i)
    {
      double uninit, a;

      for (int j = 0; j < n; ++j)
        {
        }

      a = uninit / y + n;
      if (a != 0.0)
        quux ();
    }
}

void
foo (long double x)
{
  bar<short int> (x);
  bar<int> (x);
}

% powerpc-e300c3-linux-gnu-g++-12.0.1 -mno-vsx -O1 -fcompare-debug
-frename-registers -c vrsxlrxu.cpp
powerpc-e300c3-linux-gnu-g++-12.0.1: error: vrsxlrxu.cpp: '-fcompare-debug'
failure

-fno-rename-registers or -mvsx "fixes" it.

gdk diff attached.

             reply	other threads:[~2022-03-03 12:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 12:56 asolokha at gmx dot com [this message]
2022-04-01 18:11 ` [Bug rtl-optimization/104771] " bergner at gcc dot gnu.org
2022-08-03  3:07 ` asolokha at gmx dot com
2022-08-03  3:17 ` linkw 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-104771-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).