public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl dot washington dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/19925] New: Implied do-loop in an initialization expression is broken
Date: Sat, 12 Feb 2005 21:10:00 -0000	[thread overview]
Message-ID: <20050212162133.19925.sgk@troutmask.apl.washington.edu> (raw)

>From Richard Maine, editor of the F2003 standard

   program stuff
     integer :: i_do
     integer :: i(101) = (/ (i_do, i_do=1,101) /)
     write (*,*) i
   end program stuff

   bug1.f90: In function 'MAIN__':
   bug1.f90:4: internal compiler error: Possible frontend bug: array 
   constructor not expanded

   Note that it works up to size 100; fails at size 101.

If we look in array.c, we find the magic number 100.

/* This parameter is the size of the largest array constructor that we
   will expand to an array constructor without iterators.
   Constructors larger than this will remain in the iterator form.  */

#define GFC_MAX_AC_EXPAND 100

-- 
           Summary: Implied do-loop in an initialization expression is
                    broken
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: sgk at troutmask dot apl dot washington dot edu
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2005-02-12 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-12 21:10 sgk at troutmask dot apl dot washington dot edu [this message]
2005-02-12 21:17 ` [Bug fortran/19925] " pinskia at gcc dot gnu dot org
2005-05-14 20:58 ` pinskia at gcc dot gnu dot org
2005-07-28 11:56 ` erik dot edelmann at iki dot fi

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=20050212162133.19925.sgk@troutmask.apl.washington.edu \
    --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).