public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34828] ICE: GNU MP: Cannot reallocate memory for gfortran.dg/parameter_array_init_3.f90
Date: Wed, 30 Jan 2008 15:55:00 -0000 [thread overview]
Message-ID: <20080130141615.27991.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34828-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from dominiq at lps dot ens dot fr 2008-01-30 14:16 -------
I have applied the patch on top of rev. 131960 on i686-apple-darwin9. The only
change I have noticed is that the ICE for he code in comment #10 has been
replaced by the following (cryptic) error:
pr34828_1.f90:6.80:
teger(1), parameter :: ARR1(len(HEX1)/2) = (/( MSKa1(i), i=1,len(HEX1),2)/)
1
Error: Initialization expression didn't reduce (1)
...
(I can now see why the code is invalid!-).
For pr19925 codes, I still have the same ICEs as before the patch:
[karma] f90/bug% cat pr19925_1.f90
INTEGER, PARAMETER :: N=100000
INTEGER, PARAMETER :: I(N)=(/(MOD(K,2),K=1,N)/)
INTEGER, PARAMETER :: M(N)=I(N:1:-1)
END
[karma] f90/bug% gfc pr19925_1.f90
f951: internal compiler error: Bus error
...
[karma] f90/bug% cat pr19925_3.f90
program stuff
integer :: i_do
integer :: i(100001) = (/ (i_do, i_do=1,100001) /)
write (*,*) i(100001)
end program stuff
karma] f90/bug% gfc pr19925_3.f90
pr19925_3.f90: In function 'stuff':
pr19925_3.f90:1: internal compiler error: Possible frontend bug: array
constructor not expanded
...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34828
next prev parent reply other threads:[~2008-01-30 14:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 16:15 [Bug fortran/34828] New: " burnus at gcc dot gnu dot org
2008-01-18 6:12 ` [Bug fortran/34828] " jvdelisle at gcc dot gnu dot org
2008-01-18 7:13 ` kargl at gcc dot gnu dot org
2008-01-18 23:33 ` jvdelisle at gcc dot gnu dot org
2008-01-20 3:41 ` kargl at gcc dot gnu dot org
2008-01-25 23:31 ` danglin at gcc dot gnu dot org
2008-01-28 9:10 ` jvdelisle at gcc dot gnu dot org
2008-01-28 9:17 ` jvdelisle at gcc dot gnu dot org
2008-01-28 9:21 ` jvdelisle at gcc dot gnu dot org
2008-01-28 9:53 ` dominiq at lps dot ens dot fr
2008-01-29 5:18 ` jvdelisle at gcc dot gnu dot org
2008-01-29 5:53 ` jvdelisle at gcc dot gnu dot org
2008-01-30 6:57 ` jvdelisle at gcc dot gnu dot org
2008-01-30 15:55 ` dominiq at lps dot ens dot fr [this message]
2008-01-30 18:29 ` Jerry_V_DeLisle at rl dot gov
2008-03-25 2:53 ` jvdelisle at gcc dot gnu dot org
2008-04-30 22:37 ` kargl at gcc dot gnu dot org
2008-05-26 17:05 ` jvdelisle at gcc dot gnu dot org
2008-05-28 17:27 ` fxcoudert at gcc dot gnu dot org
2008-08-08 20:54 ` jv244 at cam dot ac dot uk
2008-08-08 21:08 ` dave at hiauly1 dot hia dot nrc dot ca
2008-08-09 5:17 ` kargl at gcc dot gnu dot org
2008-08-11 7:36 ` jv244 at cam dot ac dot uk
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=20080130141615.27991.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).