public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/9297: [3.2/3.3/3.4 regression] data corruption due to codegen bug (when copying.)
@ 2003-01-21 22:05 bangerth
  0 siblings, 0 replies; only message in thread
From: bangerth @ 2003-01-21 22:05 UTC (permalink / raw)
  To: chris, gcc-bugs, gcc-prs, jody, nobody

Old Synopsis: data corruption due to codegen bug (when copying.)
New Synopsis: [3.2/3.3/3.4 regression] data corruption due to codegen bug (when copying.)

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Tue Jan 21 22:05:21 2003
State-Changed-Why:
    Confirmed. This used to work until 3.0, but fails with 3.2,
    3.3 and 3.4. I'd think that this is a serious regression,
    being a wrong-code failure.
    
    To get rid of the string functions, here's a
    very slightly modified testcase that still fails:
    ---------------------------------#include <cassert>
    
    struct C {
        C(char const * s) {
          for (int i=0; i<sizeof(p); ++i) p[i]=s[i];
        }
    
        char p[64];
    };
    
    inline C make_c(C y) { return y; }
    
    int main(int argc, char * argv[])
    {
      C data("ABCDEF");
      assert(data.p[0] == 'A'); // OK
    
      C d1(data);
      assert(d1.p[0] == 'A'); // OK
    
      C d2( make_c(data) );
      assert(d2.p[0] == 'A'); // fail
    }
    ------------------------------
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9297


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2003-01-21 22:05 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-01-21 22:05 c++/9297: [3.2/3.3/3.4 regression] data corruption due to codegen bug (when copying.) bangerth

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