public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jeremy Barnes <jeremy.barnes@idilia.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 08:26:00 -0000	[thread overview]
Message-ID: <20020403162601.9444.qmail@sources.redhat.com> (raw)

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

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

 We no longer have 3.0.2, but are using 3.0.3.  The example I attached to the 
 bug report works fine under 3.0.3.  The problem still shows up in our 
 application, however, but only when using -O, not on -O2, -O3 or -O6 any 
 more.  In general, something seems to be fixed in 3.0.3 vs 3.0.2, as it is 
 much harder to reproduce, however it is still there somewhere.
 
 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.
 
 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...


             reply	other threads:[~2002-04-03 16:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03  8:26 Jeremy Barnes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-12  7:46 Gwenole Beauchesne
2002-04-08 13:06 Richard Henderson
2002-04-08 13:06 Gwenole Beauchesne
2002-04-08 12:26 Jeremy Barnes
2002-04-03 17:20 rth
2002-04-03 14:09 rth
2002-04-03 10:36 Richard Henderson
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=20020403162601.9444.qmail@sources.redhat.com \
    --to=jeremy.barnes@idilia.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).