public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41922] Diagnostic: No location shown for overlappingly initialized EQUIVALENCEd character vars
Date: Wed, 12 May 2010 12:43:00 -0000	[thread overview]
Message-ID: <20100512124314.7896.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41922-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from dfranke at gcc dot gnu dot org  2010-05-12 12:43 -------
With current trunk (r159282), we have a locus - but not the right one:
pr41922.f:11.72:

      end                                                               
                                                                        1
Error: Overlapping unequal initializers in EQUIVALENCE at (1)

(In reply to comment #0)
> Using the commented version instead, it works:
> 
>       data cstore/2*4/
>                      1
> Error: Overlapping unequal initializers in EQUIVALENCE at (1)

IMO, this should point to the EQUIVALENCE, not one of the involved DATA
statements.


-- 

dfranke at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dfranke at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2010-05-12 12:43:14
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41922


      parent reply	other threads:[~2010-05-12 12:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03  9:02 [Bug fortran/41922] New: " burnus at gcc dot gnu dot org
2010-04-18 16:44 ` [Bug fortran/41922] " dominiq at lps dot ens dot fr
2010-05-12 12:43 ` dfranke at gcc dot gnu dot org [this message]

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=20100512124314.7896.qmail@sourceware.org \
    --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).