public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Araneda, Dorian" <dorian.araneda@intel.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: RE: optimization/3329: optimization large memory copies uses kernel memcpy function without user's knowledge.
Date: Thu, 21 Jun 2001 12:56:00 -0000 [thread overview]
Message-ID: <20010621195600.5329.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR optimization/3329; it has been noted by GNATS.
From: "Araneda, Dorian" <dorian.araneda@intel.com>
To: "'Alexandre Oliva'" <aoliva@redhat.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: RE: optimization/3329: optimization large memory copies uses kern
el memcpy function without user's knowledge.
Date: Thu, 21 Jun 2001 12:50:52 -0700
i will investigate these flags.
and thier effects on this optimization
it will not be any time soon but
i will get back to you eventually.
thanks for the reply.
-----Original Message-----
From: Alexandre Oliva [ mailto:aoliva@redhat.com ]
Sent: Thursday, June 21, 2001 3:47 PM
To: dorian.araneda@intel.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: optimization/3329: optimization large memory copies uses
kernel memcpy function without user's knowledge.
Do -fno-builtin or -ffreestanding help?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next reply other threads:[~2001-06-21 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 12:56 Araneda, Dorian [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-02 2:09 rth
2001-06-21 12:56 Alexandre Oliva
2001-06-21 8:16 dorian.araneda
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=20010621195600.5329.qmail@sourceware.cygnus.com \
--to=dorian.araneda@intel.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).