public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at pci dot uzh.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47267] array constructor causing long compile times
Date: Wed, 12 Jan 2011 10:24:00 -0000 [thread overview]
Message-ID: <bug-47267-4-aQmg0mXbzk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47267-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47267
Joost VandeVondele <Joost.VandeVondele at pci dot uzh.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |compile-time-hog
Known to fail| |4.3.2, 4.6.0
--- Comment #1 from Joost VandeVondele <Joost.VandeVondele at pci dot uzh.ch> 2011-01-12 09:43:31 UTC ---
obviously removing the parameter attribute from niter makes compilation very
fast. Presumably something down this call tree should not simplify stuff for
too large constructors
#0 0x00007ffff6ca9ad9 in _int_malloc () from /lib64/libc.so.6
#1 0x00007ffff6cacaa9 in malloc () from /lib64/libc.so.6
#2 0x0000000000d9e9a9 in __gmp_default_allocate (size=8) at
../../gcc/gmp/memory.c:44
#3 0x0000000000da39f5 in __gmpz_init (x=0x14f4038) at
../../../gcc/gmp/mpz/init.c:28
#4 0x00000000004ebc39 in gfc_get_constant_expr (type=BT_INTEGER, kind=4,
where=0x136b920) at ../../gcc/gcc/fortran/expr.c:160
#5 0x00000000004ebd6b in gfc_get_int_expr (kind=<value optimized out>,
where=<value optimized out>, value=0) at ../../gcc/gcc/fortran/expr.c:215
#6 0x00000000004caf17 in gfc_simplify_iterator_var (e=0x14f3f00) at
../../gcc/gcc/fortran/array.c:1401
#7 0x00000000004f06a8 in gfc_simplify_expr (p=0x14f3f00, type=1) at
../../gcc/gcc/fortran/expr.c:1873
#8 0x00000000004c99a6 in expand_constructor (base=<value optimized out>) at
../../gcc/gcc/fortran/array.c:1540
#9 0x00000000004c9be9 in expand_expr (base=<value optimized out>) at
../../gcc/gcc/fortran/array.c:1416
#10 expand_expr (base=<value optimized out>) at
../../gcc/gcc/fortran/array.c:1515
#11 expand_iterator (base=<value optimized out>) at
../../gcc/gcc/fortran/array.c:1486
#12 expand_constructor (base=<value optimized out>) at
../../gcc/gcc/fortran/array.c:1524
#13 0x00000000004cb94d in gfc_array_size (array=0x14f4ad0,
result=0x7fffffffd830) at ../../gcc/gcc/fortran/array.c:2190
#14 0x00000000005311eb in expression_shape (e=0x14f4ad0) at
../../gcc/gcc/fortran/resolve.c:4812
#15 expression_rank (e=0x14f4ad0) at ../../gcc/gcc/fortran/resolve.c:4888
#16 0x0000000000538742 in gfc_resolve_expr (e=0x14f4ad0) at
../../gcc/gcc/fortran/resolve.c:6060
#17 0x000000000054176f in resolve_code (code=0x14f4b90, ns=0x14efed0) at
../../gcc/gcc/fortran/resolve.c:8928
#18 0x000000000054379f in resolve_codes (ns=0x14efed0) at
../../gcc/gcc/fortran/resolve.c:13478
next prev parent reply other threads:[~2011-01-12 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 10:18 [Bug fortran/47267] New: " Joost.VandeVondele at pci dot uzh.ch
2011-01-12 10:24 ` Joost.VandeVondele at pci dot uzh.ch [this message]
2011-01-12 14:11 ` [Bug fortran/47267] " burnus at gcc dot gnu.org
2011-01-13 19:56 ` jvdelisle at gcc dot gnu.org
2011-02-06 23:19 ` jvdelisle at gcc dot gnu.org
2011-02-07 0:59 ` dfranke at gcc dot gnu.org
2013-06-24 6:59 ` dominiq at lps dot ens.fr
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-47267-4-aQmg0mXbzk@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).