public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug fortran/17097] New: Large DATA initialization broken or terminally slow
@ 2004-08-19 10:23 rth at gcc dot gnu dot org
2004-08-19 11:36 ` [Bug fortran/17097] Large DATA initialization " reichelt at gcc dot gnu dot org
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: rth at gcc dot gnu dot org @ 2004-08-19 10:23 UTC (permalink / raw)
To: gcc-bugs
The following fragment
PROGRAM APSI
IMPLICIT DOUBLE PRECISION (A-H, O-Z)
DIMENSION WORK(1200000)
DATA WORK/1200000*0.0D0/
END
does not compile in under 7.5 hours. I have no idea how long it does take,
as I stopped the process.
--
Summary: Large DATA initialization broken or terminally slow
Product: gcc
Version: 3.5.0
Status: UNCONFIRMED
Keywords: compile-time-hog
Severity: normal
Priority: P2
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rth at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17097
^ permalink raw reply [flat|nested] 5+ messages in thread* [Bug fortran/17097] Large DATA initialization terminally slow 2004-08-19 10:23 [Bug fortran/17097] New: Large DATA initialization broken or terminally slow rth at gcc dot gnu dot org @ 2004-08-19 11:36 ` reichelt at gcc dot gnu dot org 2004-08-19 14:13 ` pinskia at gcc dot gnu dot org 2004-08-19 19:45 ` toon at moene dot indiv dot nluug dot nl 2 siblings, 0 replies; 5+ messages in thread From: reichelt at gcc dot gnu dot org @ 2004-08-19 11:36 UTC (permalink / raw) To: gcc-bugs ------- Additional Comments From reichelt at gcc dot gnu dot org 2004-08-19 11:36 ------- Confirmed. Here are some timings. The first column is the array length: 4000: 1.0s 5000: 2.1s 6000: 3.5s 7000: 5.0s 8000: 7.0s 9000: 9.0s 10000: 11.5s 11000: 14.0s 12000: 17.0s This is worse than quadratic! Only assuming quadratic behavior, the original example would take about 2 days on my machine. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |reichelt at gcc dot gnu dot | |org Status|UNCONFIRMED |NEW Ever Confirmed| |1 Keywords| |monitored Last reconfirmed|0000-00-00 00:00:00 |2004-08-19 11:36:53 date| | Summary|Large DATA initialization |Large DATA initialization |broken or terminally slow |terminally slow http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17097 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug fortran/17097] Large DATA initialization terminally slow 2004-08-19 10:23 [Bug fortran/17097] New: Large DATA initialization broken or terminally slow rth at gcc dot gnu dot org 2004-08-19 11:36 ` [Bug fortran/17097] Large DATA initialization " reichelt at gcc dot gnu dot org @ 2004-08-19 14:13 ` pinskia at gcc dot gnu dot org 2004-08-19 19:45 ` Toon Moene 2004-08-19 19:45 ` toon at moene dot indiv dot nluug dot nl 2 siblings, 1 reply; 5+ messages in thread From: pinskia at gcc dot gnu dot org @ 2004-08-19 14:13 UTC (permalink / raw) To: gcc-bugs ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-08-19 14:13 ------- *** This bug has been marked as a duplicate of 13465 *** -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17097 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Bug fortran/17097] Large DATA initialization terminally slow 2004-08-19 14:13 ` pinskia at gcc dot gnu dot org @ 2004-08-19 19:45 ` Toon Moene 0 siblings, 0 replies; 5+ messages in thread From: Toon Moene @ 2004-08-19 19:45 UTC (permalink / raw) To: gcc-bugzilla; +Cc: gcc-bugs pinskia at gcc dot gnu dot org wrote: > ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-08-19 14:13 ------- > > > *** This bug has been marked as a duplicate of 13465 *** > Indeed, and - Andrew - I'd pedantically add: It's dupe, dammit - if you want Slashdot, you know where to find it ! -- Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290 Saturnushof 14, 3738 XG Maartensdijk, The Netherlands Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html A maintainer of GNU Fortran 95: http://gcc.gnu.org/fortran/ ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug fortran/17097] Large DATA initialization terminally slow 2004-08-19 10:23 [Bug fortran/17097] New: Large DATA initialization broken or terminally slow rth at gcc dot gnu dot org 2004-08-19 11:36 ` [Bug fortran/17097] Large DATA initialization " reichelt at gcc dot gnu dot org 2004-08-19 14:13 ` pinskia at gcc dot gnu dot org @ 2004-08-19 19:45 ` toon at moene dot indiv dot nluug dot nl 2 siblings, 0 replies; 5+ messages in thread From: toon at moene dot indiv dot nluug dot nl @ 2004-08-19 19:45 UTC (permalink / raw) To: gcc-bugs ------- Additional Comments From toon at moene dot indiv dot nluug dot nl 2004-08-19 19:45 ------- Subject: Re: Large DATA initialization terminally slow pinskia at gcc dot gnu dot org wrote: > ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-08-19 14:13 ------- > > > *** This bug has been marked as a duplicate of 13465 *** > Indeed, and - Andrew - I'd pedantically add: It's dupe, dammit - if you want Slashdot, you know where to find it ! -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17097 ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-08-19 19:45 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2004-08-19 10:23 [Bug fortran/17097] New: Large DATA initialization broken or terminally slow rth at gcc dot gnu dot org 2004-08-19 11:36 ` [Bug fortran/17097] Large DATA initialization " reichelt at gcc dot gnu dot org 2004-08-19 14:13 ` pinskia at gcc dot gnu dot org 2004-08-19 19:45 ` Toon Moene 2004-08-19 19:45 ` toon at moene dot indiv dot nluug dot nl
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).