public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jrt at worldlinc dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/22210] gfc_conv_array_initializer weirdness
Date: Wed, 05 Jan 2011 17:57:00 -0000 [thread overview]
Message-ID: <bug-22210-4-pj7TGchMuA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-22210-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22210
John T <jrt at worldlinc dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jrt at worldlinc dot net
--- Comment #15 from John T <jrt at worldlinc dot net> 2011-01-05 17:47:45 UTC ---
Using gfortran for gcc-4.4.5 on i686 Linux, compiled here with
glib-2.7-something on Mandriva 2008.1, I got the following error while
compiling files for an old program. I looked at the gfortran source around line
4781 of varasm.c, but don't know enough to make any suggestions about the
problem. The only observation I have is that the preceding if statement assures
that pos doesn't equal totalbytes, so the >= operator shouldn't need the = in
the assert argument. I don't know what statement sets the size of the data
block (and its size).
gfortran -c -o mind.o mind.f
mind.f:457: internal compiler error: in output_constructor, at varasm.c:4781
line 454+ of mind.f contains the statements
return
end
c---------------------------------------------------------
block data general
c---------------------------------------------------------
c
common /grid/grid_on
next parent reply other threads:[~2011-01-05 17:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-22210-4@http.gcc.gnu.org/bugzilla/>
2011-01-05 17:57 ` jrt at worldlinc dot net [this message]
2012-01-13 22:23 ` pinskia at gcc dot gnu.org
2013-06-15 23:18 ` bdavis at gcc dot gnu.org
[not found] <bug-22210-253@http.gcc.gnu.org/bugzilla/>
2006-01-03 18:45 ` pinskia at gcc dot gnu dot org
2006-01-05 17:05 ` steven at gcc dot gnu dot org
2006-06-08 7:18 ` paul dot richard dot thomas at cea dot fr
2006-06-13 19:09 ` pinskia at gcc dot gnu dot org
2006-09-18 6:58 ` pault at gcc dot gnu dot org
2007-07-09 8:06 ` pinskia at gcc dot gnu dot org
2007-10-04 21:44 ` tobi at gcc dot gnu dot org
2008-01-03 17:48 ` pinskia at gcc dot gnu dot org
2009-01-03 18:07 ` dfranke at gcc dot gnu dot org
2010-02-05 3:25 ` jvdelisle at gcc dot gnu dot org
2005-06-27 23:33 [Bug fortran/22210] New: " giovannibajo at libero dot it
2005-06-27 23:46 ` [Bug fortran/22210] " pinskia at gcc dot gnu dot org
2005-06-29 22:04 ` giovannibajo at libero dot it
2005-07-09 16:51 ` pinskia at gcc dot gnu dot org
2005-09-18 6:15 ` pinskia 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-22210-4-pj7TGchMuA@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).