From: Tim Prince <n8tm@aol.com>
To: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: gfortran on cygwin needs make distclean to update correctly
Date: Wed, 24 Feb 2016 21:58:00 -0000 [thread overview]
Message-ID: <56CE2754.7020706@aol.com> (raw)
As stated in the subject, although gcc is rebuilt as required by any
updated functions (including config/i386/i386.c), gfortran is not, even
after a make clean. I suppose this is some kind of cygwin/windows
related glitch.
I noticed this while attempting to verify optimization of the .p2align
parameters, having noticed that the 4,,10 setting for most Intel CPUs
can be improved upon occasionally by advancing to 4,,12, and that some
of the newer targets are set to 4,,15 which would have the effect of
unconditional 16-byte alignment.
Other gfortran improvements were observed, apparently due to trunk
updates since my last clean build.
In a few cases, gfortran doesn't apply .p2align while gcc does for an
exact functional translation, yet gfortran benefits more consistently
from max-unroll-times=4. Effectiveness of increased unrolling seems to
depend on better alignment as well as code optimization. I suppose loop
stream detector effective buffer size may be maximized by alignment.
--
Tim Prince
reply other threads:[~2016-02-24 21:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56CE2754.7020706@aol.com \
--to=n8tm@aol.com \
--cc=fortran@gcc.gnu.org \
--cc=tprince@computer.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).