public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/32667] builtin operator= generates memcpy with overlapping memory regions Date: Sun, 08 Jul 2007 19:46:00 -0000 [thread overview] Message-ID: <20070708194619.14202.qmail@sourceware.org> (raw) In-Reply-To: <bug-32667-5307@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from rguenth at gcc dot gnu dot org 2007-07-08 19:46 ------- No, this doesn't have anything to do with aliasing. 4.3 simply inlines the memcpys. This is probably a middle-end issue with expanding structure assignments. 2.95 and 3.3 also expanded the calls inline. 3.4 does not, likewise 4.0, 4.1 and 4.2. Note that this is likely not a problem in practice as memcpy (p, p, sizeof (*p)) is difficult to implement in a way that would make it not work. So, downgrading severity. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu dot | |org Severity|major |normal Status|UNCONFIRMED |NEW Component|c++ |middle-end Ever Confirmed|0 |1 Keywords| |wrong-code Last reconfirmed|0000-00-00 00:00:00 |2007-07-08 19:46:19 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32667
next prev parent reply other threads:[~2007-07-08 19:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-07 17:55 [Bug c++/32667] New: " Raimund dot Merkert at baesystems dot com 2007-07-07 18:19 ` [Bug c++/32667] " pcarlini at suse dot de 2007-07-07 22:36 ` Raimund dot Merkert at baesystems dot com 2007-07-08 19:46 ` rguenth at gcc dot gnu dot org [this message] 2007-07-08 20:53 ` [Bug middle-end/32667] " pcarlini at suse dot de 2009-05-06 16:37 ` ppluzhnikov at google dot com [not found] <bug-32667-4@http.gcc.gnu.org/bugzilla/> 2011-12-05 17:00 ` lu_zero at gentoo dot org 2011-12-05 20:38 ` mans at mansr dot com
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=20070708194619.14202.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: linkBe 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).