From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21736 invoked by alias); 18 Nov 2002 23:56:05 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 21693 invoked by uid 71); 18 Nov 2002 23:56:04 -0000 Date: Mon, 25 Nov 2002 00:26:00 -0000 Message-ID: <20021118235604.21682.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Danny Smith Subject: Re: c++/8047: [i386] Stack corruption with exceptions Reply-To: Danny Smith X-SW-Source: 2002-11/txt/msg00928.txt.bz2 List-Id: The following reply was made to PR c++/8047; it has been noted by GNATS. From: Danny Smith 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