From: Danny Smith <dannysmith@clear.net.nz>
To: Richard Henderson <rth@redhat.com>
Cc: gcc@gcc.gnu.org, Cygwin <cygwin@cygwin.com>,
mingw-dvlpr <mingw-dvlpr@lists.sourceforge.net>
Subject: Re: stdcall lib functions with exception throwing callbacks vs Dwarf2 EH
Date: Wed, 24 Nov 2004 08:40:00 -0000 [thread overview]
Message-ID: <000401c4d1fd$112d9eb0$8c4861cb@DANNY> (raw)
In-Reply-To: <20041124003240.GA6028@redhat.com>
Richard Henderson wrote:
> On Wed, Nov 24, 2004 at 11:27:11AM +1300, Danny Smith wrote:
>> Before I pull any more hair out trying, does any one have any hints
>> on how to use an MD_FALLBACK_FRAME_STATE_FOR to workaround ...
>
> That would be wrong.
>
> I think the most likely explanation is that there's a bug in the
> dwarf2 generator for stdcall functions with -fomit-frame-pointer,
> and the problem should be attacked there.
>
There does seem to be a problem in the frame-pointer handling see:
http://gcc.gnu.org/ml/gcc/2002-11/msg00149.html
With this testcase:
void __attribute__((stdcall)) test( int a) { a; }
void snafu( void) {
test( 666);
throw 999;
}
int main( void) {
try {
snafu( );
return 0;
} catch( ...) {
return 1;
}
}
I get (today):
g++ -fno-omit-frame-pointer PASS (at all optimisation levels).
g++ -O{0|1|2} -fomit-frame-pointer -maccumulate-outgoing-args PASS.
g++ -O0 -mtune=i686 -mno-accumulate-outgoing-args -fomit-frame-pointer
FAIL
g++ -O{1,2} -mtune=i686 -mno-accumulate-outgoing-args -fomit-frame-poi
nter PASS
The optimisation flags that cause failure has changed since the original
gcc report.
Danny
next prev parent reply other threads:[~2004-11-24 8:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 22:41 Danny Smith
2004-11-24 0:47 ` Richard Henderson
2004-11-24 7:08 ` Ranjit Mathew
2004-11-24 8:08 ` Danny Smith
2004-11-24 8:26 ` Richard Henderson
2004-11-24 9:41 ` Aaron W. LaFramboise
2004-11-24 17:40 ` Richard Henderson
2004-11-24 18:19 ` Andrew Haley
2004-11-24 8:40 ` Danny Smith [this message]
2004-11-24 19:00 ` Richard Henderson
2004-11-24 19:57 ` Andrew Pinski
2004-11-24 20:02 ` Richard Henderson
2004-11-24 21:23 ` Danny Smith
2004-11-24 6:34 ` Aaron W. LaFramboise
2004-11-24 6:58 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000401c4d1fd$112d9eb0$8c4861cb@DANNY' \
--to=dannysmith@clear.net.nz \
--cc=cygwin@cygwin.com \
--cc=dannysmith@users.sourceforge.net \
--cc=gcc@gcc.gnu.org \
--cc=mingw-dvlpr@lists.sourceforge.net \
--cc=rth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).