- To: David Given <dg@xxxxxxxxxxx>
- Subject: Re: Bad code generated with -mabi=ms?
- From: Ian Lance Taylor <iant@xxxxxxxxxx>
- Date: Tue, 20 Mar 2012 15:56:04 -0700
- Cc: gcc-help@xxxxxxxxxxx
- Comment: DKIM? See http://www.dkim.org
- Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
- In-reply-to: <4F6907CD.60004@cowlark.com> (David Given's message of "Tue, 20 Mar 2012 22:42:21 +0000")
- User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
David Given <dg@xxxxxxxxxxx> writes:
> On 20/03/12 16:45, Ian Lance Taylor wrote:
> [...]
>> I can recreate this problem with gcc 4.6, but not with gcc 4.7.
>>
>> I think it's a bug in gcc 4.6 that was fixed by this patch:
>>
>> http://gcc.gnu.org/ml/gcc-patches/2011-03/msg01664.html
>
> Do you know if there are any workarounds? Installing 4.7 isn't an option
> for us, unfortunately.
>
> (Do I get the impression nobody actually uses -mabi=ms much?)
The workaround is to not use -mabi=ms when compiling in 32-bit mode. In
32-bit mode the sysv ABI and the ms ABI are almost identical. They are
significantly different in 64-bit mode.
In 32-bit mode, I think the sysv and ms ABI are identical unless you use
the -mrtd command line option.
Ian
[Linux C Programming]
[Linux Kernel]
[eCos]
[Fedora Development]
[Fedora Announce]
[Autoconf]
[The DWARVES Debugging Tools]
[Yosemite Campsites]
[Yosemite News]
[Linux GCC]