public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Colin Burgess <cburgess@qnx.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8047: [i386] Stack corruption with exceptions
Date: Tue, 04 Feb 2003 20:56:00 -0000	[thread overview]
Message-ID: <20030204205600.809.qmail@sources.redhat.com> (raw)

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

From: Colin Burgess <cburgess@qnx.com>
To: wagner@rtna.daimlerchrysler.com, king@rtna.daimlerchrysler.com,
        nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
        schroedl@rtna.daimlerchrysler.com, gcc-prs@gcc.gnu.org,
        kloeckner@rtna.daimlerchrysler.com
Cc:  
Subject: Re: c++/8047: [i386] Stack corruption with exceptions
Date: Tue, 04 Feb 2003 15:58:45 -0500

 Hey guys, I think I saw this already.  See 
 http://gcc.gnu.org/ml/gcc-bugs/2001-12/msg00522.html
 
 You can check it by seeing if -fno-defer-pop helps the problem.  If so, 
 then here is a patch for 2.95.3
 
 Index: except.c
 ===================================================================
 RCS file: /product/tools/gcc/gcc/cp/except.c,v
 retrieving revision 1.1
 retrieving revision 1.2
 diff -c -r1.1 -r1.2
 *** except.c    28 Feb 2001 18:54:56 -0000      1.1
 --- except.c    12 Dec 2001 18:03:07 -0000      1.2
 ***************
 *** 1135,1140 ****
 --- 1135,1143 ----
         expand_expr (exp, const0_rtx, VOIDmode, EXPAND_NORMAL);
       }
 
 +   /* make sure we have cleaned up the stack */
 +   do_pending_stack_adjust();
 +
     expand_internal_throw ();
   }
 
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8047 
 
 


             reply	other threads:[~2003-02-04 20:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04 20:56 Colin Burgess [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-25  0:26 Danny Smith
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=20030204205600.809.qmail@sources.redhat.com \
    --to=cburgess@qnx.com \
    --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).