public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46331] Compilation time long with simple function in array constructor
Date: Wed, 10 Nov 2010 04:58:00 -0000	[thread overview]
Message-ID: <bug-46331-4-vA1kOqLfuU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46331-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2010-11-10 04:58:23 UTC ---
Author: jvdelisle
Date: Wed Nov 10 04:58:16 2010
New Revision: 166520

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=166520
Log:
2010-11-09  Jerry DeLisle  <jvdelisle@gcc.gnu.org>
        Mikael Morin   <mikael@gcc.gnu.org>

    PR fortran/46331
    * intrinsic.c: Correctly set the pure attributes for intrinsic
    functions.
    * expr.c (check_specification_function): Remove this function and move
    its code into gfc_is_constant_expr. (gfc_is_constant_expr): Change the
    order of checks by checking for non-constant arguments first.  Then,
    check for initialization functions, followed by intrinsics.

Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/expr.c
    trunk/gcc/fortran/intrinsic.c


  parent reply	other threads:[~2010-11-10  4:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-06 15:30 [Bug fortran/46331] New: " jvdelisle at gcc dot gnu.org
2010-11-06 16:09 ` [Bug fortran/46331] " jvdelisle at gcc dot gnu.org
2010-11-07 14:33 ` jvdelisle at gcc dot gnu.org
2010-11-08  2:20 ` jvdelisle at gcc dot gnu.org
2010-11-10  4:58 ` jvdelisle at gcc dot gnu.org [this message]
2010-11-10  5:26 ` jvdelisle at gcc dot gnu.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=bug-46331-4-vA1kOqLfuU@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).