Re: optimization/5040: g++-3.0.2: -O causes variables from different stack frames to overlap

[Jeremy Barnes <jeremy dot barnes at idilia dot com>]

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...