public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/5040: g++-3.0.2: -O causes variables from different stack frames to overlap
Date: Wed, 03 Apr 2002 10:36:00 -0000	[thread overview]
Message-ID: <20020403183600.7486.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/5040; it has been noted by GNATS.

From: Richard Henderson <rth@redhat.com>
To: Jeremy Barnes <jeremy.barnes@idilia.com>
Cc: rth@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: optimization/5040: g++-3.0.2: -O causes variables from different stack frames to overlap
Date: Wed, 3 Apr 2002 10:32:19 -0800

 On Wed, Apr 03, 2002 at 11:22:59AM -0500, Jeremy Barnes wrote:
 > I don't have the time currently to bootstrap a CVS version of 3.1.  I do have 
 > some code (the relevent parts of our app distilled into a single source file) 
 > that still reproduces the problem under 3.0.3.  I can send it to an 
 > individual developer, but would prefer not to send it to a public mailing 
 > list.  Respond if you are interested.
 
 I'd like to look at it.
 
 > My suspicion is that it won't show up in 3.1 using this source file, as the 
 > example is extremely brittle.  If this is the case, then the only way to be 
 > sure it is fixed and not hiding, would be to diagnose it back on the 3.0.2 
 > branch, figure out where the problem was, and then look to see if it was 
 > fixed in 3.1.  Sounds arduous...
 
 Hmm, yes...
 
 
 r~


             reply	other threads:[~2002-04-03 18:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03 10:36 Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-12  7:46 Gwenole Beauchesne
2002-04-08 13:06 Gwenole Beauchesne
2002-04-08 13:06 Richard Henderson
2002-04-08 12:26 Jeremy Barnes
2002-04-03 17:20 rth
2002-04-03 14:09 rth
2002-04-03  8:26 Jeremy Barnes
2002-04-03  1:41 rth
2001-12-06 13:36 jeremy.barnes

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=20020403183600.7486.qmail@sources.redhat.com \
    --to=rth@redhat.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).