This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug middle-end/21939] Corrupted memory with deque of >63 items under gcc-3.4.4


------- Additional Comments From magerman at rentec dot com  2005-06-06 22:46 -------
(In reply to comment #2)
> The last time I saw a bug like this, it was actually a bug in the person's code.

I wish it were true.  We've got this code (well, a more complicated version of
it) working optimized (-O3) and unoptimized under two different compilers
(gcc-2.9.5.2 and gcc-3.2) on two different OSes (Linux and Solaris).  The
example is pretty simple and straight-forward.  It's hard to see where there can
be a bug in the code.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21939


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]