From: Tim Prince <n8tm@aol.com>
To: cygwin@cygwin.com
Subject: Re: Is the Latest Release of Cygwin supported on Windows Server 8/2012
Date: Sun, 27 May 2012 07:30:00 -0000 [thread overview]
Message-ID: <4FC17A8A.5050205@aol.com> (raw)
In-Reply-To: <4FC169D9.6090107@tlinx.org>
On 05/26/2012 07:40 PM, Linda Walsh wrote:
>
>
> Every time you fetch a word or instruction that is not 8-byte
> aligned,
> you force a fatal (but caught by the processor and/or OS) signal for
> unaligned
> data. That forces execution out of the pipeline (though not likely
> out of
> cache, sadly, due to frequency of occurrence). That's not counting
> the extra
> cycles to fetch the rest of the data. On some machines that can
> easily amount
> to several dozen instructions worth.
>
There have been compilers for 32-bit Windows for 20 years which gave
8-byte alignments by default. cygwin changed the default configure
parameter in binutils so as to support alignment about 8 years ago. It
was tolerable to some before then as it matters only for 64-bit and
larger objects (doubles, and SSE, after that was introduced). The
characteristics of the worst compiler (with respect to alignment)
available outside of cygwin don't have a bearing on this list.
If the powers that be have decided that 64-bit mode should be supported
on cygwin setup.exe only by mingw cross compilers, I'll accept that.
--
Tim Prince
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-05-27 0:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 22:15 Matt Seitz (matseitz)
2012-05-21 22:44 ` Andrew DeFaria
2012-05-21 22:50 ` Andrew DeFaria
2012-05-21 23:04 ` Matt Seitz (matseitz)
2012-05-22 0:27 ` Andrew DeFaria
2012-05-22 16:58 ` Matt Seitz (matseitz)
2012-05-26 23:43 ` Linda Walsh
2012-05-27 0:51 ` Daniel Colascione
2012-05-27 11:30 ` Linda Walsh
2012-05-27 17:37 ` Tim Prince
2012-05-27 19:19 ` Linda Walsh
2012-05-27 7:30 ` Tim Prince [this message]
2012-05-28 21:21 ` Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2012-05-18 14:46 Cary Conover
2012-05-18 14:58 ` Andrew DeFaria
2012-05-18 17:59 ` James Johnston
2012-05-18 22:46 ` Andrew DeFaria
2012-05-18 23:38 ` JonY
2012-05-19 1:15 ` Andrew DeFaria
2012-05-19 2:40 ` JonY
2012-05-19 3:26 ` Andrew DeFaria
2012-05-19 5:05 ` JonY
2012-05-21 17:36 ` James Johnston
2012-05-21 20:01 ` Andrew DeFaria
2012-05-21 17:18 ` James Johnston
2012-05-21 17:35 ` Andrew DeFaria
2012-05-21 20:49 ` Warren Young
2012-05-21 21:30 ` Andrew DeFaria
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=4FC17A8A.5050205@aol.com \
--to=n8tm@aol.com \
--cc=cygwin@cygwin.com \
--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).