From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28807 invoked by alias); 13 Jan 2005 10:49:59 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 27316 invoked by alias); 13 Jan 2005 10:47:27 -0000 Date: Thu, 13 Jan 2005 10:49:00 -0000 Message-ID: <20050113104727.27312.qmail@sourceware.org> From: "baldrick at free dot fr" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050112225244.19410.baldrick@free.fr> References: <20050112225244.19410.baldrick@free.fr> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug middle-end/19410] Overlapping memcpy with big struct copies (ACATS c64106a) X-Bugzilla-Reason: CC X-SW-Source: 2005-01/txt/msg01658.txt.bz2 List-Id: ------- Additional Comments From baldrick at free dot fr 2005-01-13 10:47 ------- Subject: Re: Overlapping memcpy with big struct copies (ACATS c64106a) > > Would you like me to file a separate report for them? Here is cxa4009 by the way: > > Yes please because this is a related issue but I think it might be an Ada front-end bug rather than what > C64106A is which is a middle-end one as shown by the C example. I filed a separate bug report for CXA4009 and CXA4020: [Bug ada/19419]. By the way, I've tried to imagine how a memcpy with source==target can cause problems, without much success. Any hints? :) The only thing I could come up with was: if there are two copies of the same bit of memory (eg: one in cache, the other in main memory; or one in backing store, one in memory), with one copy being out of date; and the memcpy causing the out-of-date one to be written on top of the up-to-date one somehow... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19410