public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vivekrao4 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30319] New: internal error in gfc_resolve_expr() for character parameter
Date: Thu, 28 Dec 2006 19:13:00 -0000 [thread overview]
Message-ID: <bug-30319-9647@http.gcc.gnu.org/bugzilla/> (raw)
U:\vrao\fortran>type gfort_bug_returns.f90
module amod
character (len=1), parameter :: aa = "z", bb(1) = (/aa/)
end module amod
U:\vrao\fortran>gfortran -v
Using built-in specs.
Target: i386-pc-mingw32
Configured with: ../trunk/configure --prefix=/mingw
--enable-languages=c,fortran --with-gmp=/home/coudert/local --disable-nls
--with-ld=/mingw/bin/ld --with-as=/mingw/bin/as --disable-werror
--enable-bootstrap --enable-threads --host=i386-pc-mingw32 --disable-shared
--enable-libgomp
Thread model: win32
gcc version 4.3.0 20061021 (experimental)
U:\vrao\fortran>gfortran -c gfort_bug_returns.f90
In file gfort_bug_returns.f90:3
end module amod
1
Internal Error at (1):
gfc_resolve_expr(): Bad expression type
--
Summary: internal error in gfc_resolve_expr() for character
parameter
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: vivekrao4 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30319
next reply other threads:[~2006-12-28 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 19:13 vivekrao4 at yahoo dot com [this message]
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
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=bug-30319-9647@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).