From: Daniel Jacobowitz <dan@debian.org>
To: Long Li <long21st@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: memcpy embedded in gcc?
Date: Thu, 13 Feb 2003 15:14:17 -0500 [thread overview]
Message-ID: <20030213201417.GA12200@nevyn.them.org> (raw)
In-Reply-To: <20030213200757.92340.qmail@web40411.mail.yahoo.com>
On Thu, Feb 13, 2003 at 12:07:57PM -0800, Long Li wrote:
> Hi,
>
> I am using a gcc 3.0.4 MIPS crosscompiler on Redhat. I
> found something interesting: when I use specifly -O1
> for compilation, and I can use memcpy function even I
> did not tell the compiler where I declard it or define
> it. However, when I specify -O0, then the compiler
> tells me undefined reference to this memcpy function.
> So my questions are:
>
> 1. Is memcpy a built-in function for gcc? But why not
> for optimization level 0?
Because using it is an optimization.
> 2. Besides memcpy, is there any other functions built
> in too?
Lots. The list varies depending on the GCC version; see the manual.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-02-13 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 20:07 memcpy embedded in gcc? Long Li
2003-02-13 20:14 ` Daniel Jacobowitz [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=20030213201417.GA12200@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=long21st@yahoo.com \
/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