public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Danny Smith <dannysmith@clear.net.nz>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8047: [i386] Stack corruption with exceptions
Date: Mon, 25 Nov 2002 00:26:00 -0000	[thread overview]
Message-ID: <20021118235604.21682.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/8047; it has been noted by GNATS.

From: Danny Smith <dannysmith@clear.net.nz>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/8047: [i386] Stack corruption with exceptions
Date: Mon, 18 Nov 2002 23:51:15 +0000

 [The following observations are for mingw32 and cygwin builds with
 Dwarf2 EH enabled.  The patches to enable Dwarf2 are in the
 cygwin-mingw-gcc-3_2-branch.]
 
 I have just tried this with i386-mingw32 (GCC3.3) with same result: Okay
 with
 march=i686, stack exhaustion with  i[345]86.  However, if add
 -maccumulate-ougoing-args, the stack is okay with default  -march=i386
 
 Ditto with cygwin
 
 
 Coincidentally, in mingw and cygwin, functions that call a __stdcall
 function
 (callee pops stack) show stack corruption with Dwarf2 exceptions when
 compiled with
 -fomit-frame-pointer, but are okay with -fomit-frame-pointer
 -maccumulate-outgoing-args.
 
 Also, perhaps related is PR6764, which still fails on mingw
 with --march=i386
 but not with -march=i686 or -maccumulate-outgoing-args
 
 Danny
 
 


             reply	other threads:[~2002-11-18 23:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25  0:26 Danny Smith [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-04 20:56 Colin Burgess
2002-11-21 17:52 Wolfgang Bangerth

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=20021118235604.21682.qmail@sources.redhat.com \
    --to=dannysmith@clear.net.nz \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).