public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "baldrick at free dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/19410] Overlapping memcpy with big struct copies (ACATS c64106a)
Date: Thu, 13 Jan 2005 10:49:00 -0000 [thread overview]
Message-ID: <20050113104727.27312.qmail@sourceware.org> (raw)
In-Reply-To: <20050112225244.19410.baldrick@free.fr>
------- 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
next prev parent reply other threads:[~2005-01-13 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 22:52 [Bug ada/19410] New: ACATS c64106a - valgrind detects wrong code (overlapping memcpy) baldrick at free dot fr
2005-01-12 23:12 ` [Bug ada/19410] " baldrick at free dot fr
2005-01-12 23:36 ` [Bug middle-end/19410] Overlapping memcpy with big struct copies (ACATS c64106a) pinskia at gcc dot gnu dot org
2005-01-12 23:52 ` baldrick at free dot fr
2005-01-12 23:57 ` pinskia at gcc dot gnu dot org
2005-01-13 0:08 ` baldrick at free dot fr
2005-01-13 0:13 ` pinskia at gcc dot gnu dot org
2005-01-13 10:49 ` baldrick at free dot fr [this message]
2005-02-24 19:00 ` bosch at gcc dot gnu dot org
2005-02-24 21:23 ` ebotcazou at gcc dot gnu dot org
2005-09-12 7:12 ` [Bug middle-end/19410] Overlapping memcpy with big struct copies ebotcazou at gcc dot gnu dot org
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=20050113104727.27312.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).