public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hanzac at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/3329] optimization large memory copies uses kernel memcpy function without user's knowledge.
Date: Fri, 15 Jul 2005 08:46:00 -0000 [thread overview]
Message-ID: <20050715082622.21228.qmail@sourceware.org> (raw)
In-Reply-To: <20010621081601.3329.dorian.araneda@intel.com>
------- Additional Comments From hanzac at gmail dot com 2005-07-15 08:26 -------
> Anyway, like (nearly) all optimizations in gcc, it can be turned off by
turning off optimization for the affected file.
It can't be turned off when using MinGW GCC. I hope there will be a
option to enable or disable this feature that auto-emits memcpy.
Because when developing a OS kernel, external memcpy to link is not
available, of course.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3329
prev parent reply other threads:[~2005-07-15 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010621081601.3329.dorian.araneda@intel.com>
2003-07-14 20:11 ` [Bug optimization/3329] " dorian dot araneda at intel dot com
2003-07-14 21:09 ` pinskia at physics dot uc dot edu
2003-07-15 0:08 ` neroden at gcc dot gnu dot org
2005-07-15 8:46 ` hanzac at gmail dot com [this message]
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=20050715082622.21228.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).