public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30319] internal error in gfc_resolve_expr() for character parameter
Date: Thu, 28 Dec 2006 19:37:00 -0000	[thread overview]
Message-ID: <20061228193745.31660.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30319-9647@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from kargl at gcc dot gnu dot org  2006-12-28 19:37 -------
The following appears to work, so Vivek if you have a critical 
need to get an application compiled.  You can split the line.

module amod
! The following is a work around.
  character (len=1), parameter :: aa = "z"
  character (len=1), parameter :: bb(1) = (/ aa /)
end module amod


-- 

kargl at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu dot org


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


  parent reply	other threads:[~2006-12-28 19:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28 19:13 [Bug fortran/30319] New: " vivekrao4 at yahoo dot com
2006-12-28 19:19 ` [Bug fortran/30319] " pinskia at gcc dot gnu dot org
2006-12-28 19:37 ` kargl at gcc dot gnu dot org [this message]
2007-01-22 23:54 ` fxcoudert at gcc dot gnu dot org
2007-02-10 21:15 ` patchapp at dberlin dot org
2007-02-11 20:59 ` pault at gcc dot gnu dot org
2007-02-12 22:58 ` [Bug fortran/30319] [4.2 and 4.1 only] " pault at gcc dot gnu dot org
2007-02-17 17:17 ` pault at gcc dot gnu dot org
2007-02-17 17:20 ` pault 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=20061228193745.31660.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).