[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: MinGW and -fomit-frame-pointer problem cleared up
- From: Mike Pall <mikelu-0602@...>
- Date: Thu, 16 Feb 2006 01:29:51 +0100
it has been mentiond on the list a few times that there are
mysterious failures with MinGW/Cygwin when compiling with
I've tracked this down and found a corresponding bug report:
It's basically a wrong generation of unwind info for stdcalls,
but only when the outgoing args are not accumulated. This happens
only under some, but not all optimization and CPU type settings.
The fix is available starting with GCC 4.0. It has not been
backported to GCC 3.x.
A suggested workaround for GCC 3.x is to always use two flags:
Hope this saves someone else a few days of bug hunting ...