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/19419] ACATS CXA4009, CXA4020 - valgrind detects bad code (overlapping memcpy)
Date: Sat, 15 Jan 2005 12:28:00 -0000	[thread overview]
Message-ID: <20050115122755.9693.qmail@sourceware.org> (raw)
In-Reply-To: <20050113075308.19419.baldrick@free.fr>


------- Additional Comments From baldrick at free dot fr  2005-01-15 12:27 -------
Subject: Re:  ACATS CXA4009, CXA4020 - valgrind detects bad code (overlapping memcpy)

> Confirmed, the problem is in gimplify_modify_expr_to_memcpy (but this is not a regression even 
> though this is a middle-end problem).

Are you sure?  The memcpy is already there in the generic tree (based on the dumps), and doesn't
gimplification happen later?  Also, the memcpy problem goes back to GNAT 3.15p, which is based on
gcc 2.8.1.


-- 


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


  parent reply	other threads:[~2005-01-15 12:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13  7:53 [Bug ada/19419] New: " baldrick at free dot fr
2005-01-14  8:59 ` [Bug ada/19419] " baldrick at free dot fr
2005-01-14 23:23 ` baldrick at free dot fr
2005-01-14 23:35 ` [Bug middle-end/19419] " pinskia at gcc dot gnu dot org
2005-01-14 23:36 ` pinskia at gcc dot gnu dot org
2005-01-15 12:28 ` baldrick at free dot fr [this message]
2005-01-15 12:34 ` [Bug ada/19419] " steven at gcc dot gnu dot org
2005-01-15 16:27 ` [Bug middle-end/19419] " pinskia at gcc dot gnu dot org
2005-09-12  6:14 ` [Bug middle-end/19419] Overlapping memcpy with discriminated types ebotcazou at gcc dot gnu dot org
2005-09-12  7:27 ` 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=20050115122755.9693.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).