DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=YIqQOpHv0D6SanGoELjBDrHeK8PTSbHRY9anOBDO9dW
	oNxPf3ZLH5IgWK6luY+zbs2HpP/yRFcyMFKOykpaW+Vh6QQn8kbGYsvnYkvgE3hU
	Fje/xtdE4iQROpCikdkcBHfcnY3Zri+VuTLTkAhnPHYujzmSPC3cH68+I0y9KX8o
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <52633B25.8070104@etr-usa.com>
Date: Sat, 19 Oct 2013 20:08:37 -0600
From: Warren Young <warren@etr-usa.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: g++ -m32 option causes an error
References: <bug-58799-23798@http.gcc.gnu.org/bugzilla/> <bug-58799-23798-jpgPVpVU2B@http.gcc.gnu.org/bugzilla/> <1382135640.94420.YahooMailNeo@web181306.mail.ne1.yahoo.com> <1382135893.8524.YahooMailNeo@web181304.mail.ne1.yahoo.com> <1382210427.30799.YahooMailNeo@web181305.mail.ne1.yahoo.com>
In-Reply-To: <1382210427.30799.YahooMailNeo@web181305.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 10/19/2013 13:20, Arthur Schwarz wrote:
>
> What I want is the compiler to generate 32-bit code loadable
> on a 64-bit and a 32-bit platform. This is possible using the 32-bit
> cygwin compilers.

Yes, it's possible, but it may not do what you expect.

64-bit Cygwin can blindly launch a 32-bit Cygwin program (and vice 
versa) but none of the cross-process mechanisms that involve cygwin1.dll 
will work since the two programs will be running under different 
versions of the DLL.

Whether this matters or not depends on what Program A (64-bit) is asking 
Program B (32-bit) to do for it.  Program B can't access a POSIX shared 
memory segment set up by Program A, for example.

> I don't understand why there is not x86_64-pc-cygwin assembler

There is.  It's called as(1) and you run it from 64-bit Cygwin.

The only reason you need to give the long platform prefix on these 
commands is when you're doing cross-compilation.  So, say g++ instead of 
bla-bla-bla-g++.

Now, if you're asking why there is no 64-bit *cross-assembler* for use 
on 32-bit Cygwin, I'd guess that's because no one has needed it yet.

--
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