Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	N8TM AT aol DOT com
Message-ID:	<38.17b91ac.25c4a493@aol.com>
Date:	Sat, 29 Jan 2000 15:16:19 EST
Subject:	Re: LARGE_INTEGER in w32API 0.1.5
To:	khan AT nanotech DOT wisc DOT edu
CC:	kris DOT thielemans AT csc DOT mrc DOT ac DOT uk, anorland AT hem DOT passagen DOT se,
	cygwin AT sourceware DOT cygnus DOT com
MIME-Version:	1.0
X-Mailer:	AOL 5.0 for Windows sub 68

I've been building gcc snapshots with the minimum of modifications, not 
wanting any special features, just to make the standard ones work.

I have used both an older patch of yours to handle 2 versions of 
LARGE_INTEGER (no anonymous union) and a simple hack where all the variables 
are long long int and are passed to the API functions with a cast 
(LARGE_INTEGER *)&variable, but it gets old having to patch every gcc 
snapshot.

BTW, I found that my g++ testsuite crashes on the Kayak at the office came 
from the use of an out of date binutils snapshot which actually was worse in 
that respect than standard cygwinB20.1 plus snapshot patches.  Both the 
binary from your site and newer egcs infrastructure sources work fine, and 
set up .p2align automatically, which the standard cygwin doesn't do with 
gcc-2.96, although it did with gcc-2.95.  The difference is mainly in the 
amount of useless 128-bit padding which gcc-2.96 does without .p2align.  The 
padding would be more useful if cygwin kept the stack aligned etc.

Tim

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -