From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Sebastian Pop <sebpop@gmail.com>
Cc: Mark Mitchell <mark@codesourcery.com>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: HIRLAM with -ftree-loop-distribution.
Date: Sun, 16 Dec 2007 19:43:00 -0000 [thread overview]
Message-ID: <476573D9.1060301@moene.indiv.nluug.nl> (raw)
In-Reply-To: <cb9d34b20712160918h489a5938t28da9b61e384710c@mail.gmail.com>
Sebastian Pop wrote:
> Wow! Thanks for the numbers. I guess from your message that there
> were no ICEs or other problems with the loop distribution patch.
Exactly.
--
Toon Moene - e-mail: toon@moene.indiv.nluug.nl - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
At home: http://moene.indiv.nluug.nl/~toon/
GNU Fortran's path to Fortran 2003: http://gcc.gnu.org/wiki/Fortran2003
next prev parent reply other threads:[~2007-12-16 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 12:31 Toon Moene
2007-12-16 17:53 ` Sebastian Pop
2007-12-16 19:43 ` Toon Moene [this message]
2007-12-16 12:44 Uros Bizjak
2007-12-16 13:34 ` Toon Moene
2007-12-16 14:14 ` Dorit Nuzman
2007-12-16 14:54 ` Dorit Nuzman
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=476573D9.1060301@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=sebpop@gmail.com \
/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).