X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Erik van der Kouwe Subject: Re: Inconsistency between winnt.h header in /usr/include/w32api and the one supplied with the Microsoft SDK Date: Wed, 28 Sep 2011 09:02:25 +0000 (UTC) Lines: 19 Message-ID: References: <4E82CF78 DOT 7090405 AT cs DOT vu DOT nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hi, > the issue you are noticing here is that pdata information differs > between different archtiectures. The first you have shown here is the > definition of the spark,mips, and (IIRC) arm architecture. The second > one you've shown is the definition of pdata for x64 architecture. For > x86 itself there is no pdata-information present, as x86 is using > stack-based SEH support, and not table-based one as other > architectures. Thanks for your answer. That makes sense. Still, Windows makes the x64 version available even on x86 architectures. I guess this makes sense as Windows no longer runs on those other architectures architectures these days. x86 Cygwin is likely to run on many x64 systems and encounter x64 binaries (which is also what I'm using it for). With kind regards, Erik -- 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