public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33818]  New: [Regression 4.3]  Bogus error "Variable 'str' is used at (1) before the ENTRY statement"
Date: Fri, 19 Oct 2007 14:54:00 -0000	[thread overview]
Message-ID: <bug-33818-13404@http.gcc.gnu.org/bugzilla/> (raw)

Reduced from http://gcc.gnu.org/ml/fortran/2007-10/msg00280.html

The following gives the bogus error:

  write(lu,'(a)') 'UNIT '//UpperCase(UNAME(1))
                                             1
Error: Variable 'str' is used at (1) before the ENTRY statement in which it is
a parameter

subroutine ExportZMX(lu)
  implicit real(selected_real_kind(15)) (a-h,o-z)
  character(*),parameter :: UNAME(1:1)=(/'XXX'/)
  write(lu,'(a)') 'UNIT '//UpperCase(UNAME(1))
  entry ExportSEQ(lu)
contains
  function UpperCase(str) result(res)
    character(*),intent(in) :: str
    character(len(str)) res
    res=str
  end function
end


-- 
           Summary: [Regression 4.3]  Bogus error "Variable 'str' is used at
                    (1) before the ENTRY statement"
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Keywords: rejects-valid
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org


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


             reply	other threads:[~2007-10-19 14:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19 14:54 burnus at gcc dot gnu dot org [this message]
2007-10-19 15:07 ` [Bug fortran/33818] " dominiq at lps dot ens dot fr
2007-10-19 15:10 ` tobi at gcc dot gnu dot org
2007-10-19 15:13 ` dominiq at lps dot ens dot fr
2007-10-19 15:15 ` burnus at gcc dot gnu dot org
2007-10-19 21:16 ` [Bug fortran/33818] [4.3 Regression] " burnus at gcc dot gnu dot org
2007-10-20  4:24 ` patchapp at dberlin dot org
2007-10-20 11:34 ` burnus at gcc dot gnu dot org
2007-10-20 11:39 ` burnus at gcc dot gnu dot 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-33818-13404@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).