This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: g++ -m32 option causes an error
- From: Warren Young <warren at etr-usa dot com>
- To: Cygwin-L <cygwin at cygwin dot com>
- Date: Sat, 19 Oct 2013 20:08:37 -0600
- Subject: Re: g++ -m32 option causes an error
- Authentication-results: sourceware.org; auth=none
- References: <bug-58799-23798 at http dot gcc dot gnu dot org/bugzilla/> <bug-58799-23798-jpgPVpVU2B at http dot gcc dot gnu dot org/bugzilla/> <1382135640 dot 94420 dot YahooMailNeo at web181306 dot mail dot ne1 dot yahoo dot com> <1382135893 dot 8524 dot YahooMailNeo at web181304 dot mail dot ne1 dot yahoo dot com> <1382210427 dot 30799 dot YahooMailNeo at web181305 dot mail dot ne1 dot yahoo dot com>
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