public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/94329] New: gcc-9: error: use_only.f90: ‘-fcompare-debug’ failure (length)
Date: Wed, 25 Mar 2020 13:55:30 +0000	[thread overview]
Message-ID: <bug-94329-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 94329
           Summary: gcc-9: error: use_only.f90: ‘-fcompare-debug’ failure
                    (length)
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: jakub at gcc dot gnu.org
  Target Milestone: ---

Fails since GCC 4.9.0:

$ cat use_only.f90
SUBROUTINE r_to_s1b ( s, hinv )
REAL hinv(:,:)     
DO I=1,3
DO J=1,3
S = hinv(i,j)
END DO
END DO
END

$ gcc -Werror -fcompare-debug -O1 -fno-tree-loop-optimize -fwrapv -c
use_only.f90
gcc: error: use_only.f90: ‘-fcompare-debug’ failure (length)

             reply	other threads:[~2020-03-25 13:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 13:55 marxin at gcc dot gnu.org [this message]
2020-03-25 13:55 ` [Bug debug/94329] " marxin at gcc dot gnu.org
2020-03-26 14:27 ` [Bug debug/94329] [8/9/10 Regression] " jakub at gcc dot gnu.org
2020-03-27 14:53 ` [Bug tree-optimization/94329] " jakub at gcc dot gnu.org
2020-03-27 14:58 ` jakub at gcc dot gnu.org
2020-03-28  9:22 ` cvs-commit at gcc dot gnu.org
2020-03-28  9:24 ` [Bug tree-optimization/94329] [8/9 " jakub at gcc dot gnu.org
2020-04-07 19:04 ` cvs-commit at gcc dot gnu.org
2020-04-07 20:02 ` [Bug tree-optimization/94329] [8 " jakub at gcc dot gnu.org
2020-09-17 17:23 ` jakub 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-94329-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).