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/105464] New: '-fcompare-debug' failure (length) w/ -Og -fharden-compares -fno-tree-dce
Date: Tue, 03 May 2022 10:12:37 +0000	[thread overview]
Message-ID: <bug-105464-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105464
           Summary: '-fcompare-debug' failure (length) w/ -Og
                    -fharden-compares -fno-tree-dce
           Product: gcc
           Version: 13.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: x86_64-unknown-linux-gnu

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

gcc 13.0.0 20220501 snapshot (g:75bbc3da3e5f75f683fa33e309045c582efd20eb) fails
-fcompare-debug check when compiling
gcc/testsuite/gcc.c-torture/compile/pr46547-1.c w/ -Og -fharden-compares
-fno-tree-dce:

% x86_64-unknown-linux-gnu-gcc-13.0.0 -Og -fcompare-debug -fharden-compares
-fno-tree-dce -c sqnqheby.c
x86_64-unknown-linux-gnu-gcc-13.0.0: error: sqnqheby.c: '-fcompare-debug'
failure (length)

gkd diff attached.

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 10:12 asolokha at gmx dot com [this message]
2022-05-03 10:31 ` [Bug debug/105464] " marxin at gcc dot gnu.org
2022-10-31 16:06 ` [Bug target/105464] " pinskia at gcc dot gnu.org
2022-12-14 13:03 ` asolokha at gmx dot com

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-105464-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).