public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/12366] [4.0 only] array assignment fails
Date: Sun, 18 Sep 2005 09:51:00 -0000	[thread overview]
Message-ID: <20050918095142.17513.qmail@sourceware.org> (raw)
In-Reply-To: <20030922131506.12366.tcc@sentex.net>


------- Additional Comments From tkoenig at gcc dot gnu dot org  2005-09-18 09:51 -------
This is not fixed in 4.0.2:

$ cat pr12366.f90
program testg
  real, dimension(5) :: a=(/ 1.5,2.1,3.2,4.6,5.3 /)
  integer,dimension(3) :: i
  i=(/ 2,3,1 /)
  print *, a((/ 2,3,1 /))       ! ICEs
  ! print *, a(i)                               !works fine
end program testg
$ gfortran pr12366.f90
pr12366.f90: In function 'MAIN__':
pr12366.f90:5: internal compiler error: in gfc_conv_ss_descriptor, at
fortran/trans-array.c:1235
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
$ gfortran -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.0/configure --prefix=/home/ig25
--enable-languages=c,fortran
Thread model: posix
gcc version 4.0.2 20050917 (prerelease)

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
      Known to fail|                            |4.0.2
      Known to work|                            |4.1.0
         Resolution|FIXED                       |
            Summary|array assignment fails      |[4.0 only] array assignment
                   |                            |fails


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


  parent reply	other threads:[~2005-09-18  9:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22 14:24 [Bug fortran/12366] New: " tcc at sentex dot net
2003-09-26  7:06 ` [Bug fortran/12366] " toon at moene dot indiv dot nluug dot nl
2003-09-27  6:28 ` pinskia at gcc dot gnu dot org
2004-01-25 17:47 ` [Bug fortran/12366] [gfortran] " dhazeghi at yahoo dot com
2004-04-22 11:52 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2004-05-05 16:25 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2004-05-05 16:57 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2004-05-26 22:55 ` pinskia at gcc dot gnu dot org
2004-06-13  9:06 ` pinskia at gcc dot gnu dot org
2004-10-05 18:08 ` [Bug fortran/12366] " pinskia at gcc dot gnu dot org
2004-10-08 21:36 ` pinskia at gcc dot gnu dot org
2004-11-08 18:11 ` pinskia at gcc dot gnu dot org
2004-12-10  9:54 ` paulthomas2 at wanadoo dot fr
2004-12-13 13:52 ` Thomas dot Koenig at online dot de
2005-03-26 22:02 ` pinskia at gcc dot gnu dot org
2005-06-28  1:19 ` pinskia at gcc dot gnu dot org
2005-09-18  5:06 ` pinskia at gcc dot gnu dot org
2005-09-18  9:51 ` tkoenig at gcc dot gnu dot org [this message]
2005-09-18 16:53 ` [Bug fortran/12366] [4.0 only] " pinskia at gcc dot gnu dot org
2005-09-18 20:03 ` pinskia at gcc dot gnu dot org
2005-09-18 20:27 ` 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=20050918095142.17513.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).