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/34554] time compiling complicated size initialization expression Date: Sun, 11 Apr 2010 08:11:00 -0000 [thread overview] Message-ID: <20100411081101.11328.qmail@sourceware.org> (raw) In-Reply-To: <bug-34554-10391@http.gcc.gnu.org/bugzilla/> ------- Comment #10 from dominiq at lps dot ens dot fr 2010-04-11 08:11 ------- With the patch in comment #9 applied to the fortran-exp branch, the timing for the original test is slightly slower than trunk ~250s compared to ~240s. Note that the procedure node_copy_and_append should be deleted otherwise you get the error: cc1: warnings being treated as errors ../../cons_clean/gcc/fortran/constructor.c:65:1: error: 'node_copy_and_append' defined but not used make[3]: *** [fortran/constructor.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[2]: *** [all-stage2-gcc] Error 2 make[1]: *** [stage2-bubble] Error 2 make: *** [all] Error 2 Thanks for the patch. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34554
next prev parent reply other threads:[~2010-04-11 8:11 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-12-22 10:56 [Bug fortran/34554] New: " tkoenig at gcc dot gnu dot org 2007-12-22 11:44 ` [Bug fortran/34554] " pinskia at gcc dot gnu dot org 2007-12-22 12:19 ` dfranke at gcc dot gnu dot org 2008-09-14 19:11 ` dominiq at lps dot ens dot fr 2009-01-03 22:13 ` dfranke at gcc dot gnu dot org 2010-04-10 15:41 ` jvdelisle at gcc dot gnu dot org 2010-04-10 15:51 ` dfranke at gcc dot gnu dot org 2010-04-11 1:49 ` jvdelisle at gcc dot gnu dot org 2010-04-11 6:39 ` jvdelisle at gcc dot gnu dot org 2010-04-11 6:44 ` jvdelisle at gcc dot gnu dot org 2010-04-11 8:11 ` dominiq at lps dot ens dot fr [this message] 2010-04-11 8:26 ` dominiq at lps dot ens dot fr 2010-04-11 13:08 ` jvdelisle at gcc dot gnu dot org 2010-04-15 0:35 ` jvdelisle 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=20100411081101.11328.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: linkBe 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).