public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Rolf Fiedler <rfie@majestix.ferrari.de>
To: Pete Popov <ppopov@redcreek.com>
Cc: crossgcc@cygnus.com
Subject: Re: your mail
Date: Wed, 20 May 1998 06:06:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.95.980520102050.305A-100000@miraculix.ferrari.de> (raw)
In-Reply-To: <3561BA5A.B421C781@redcreek.com>

On Tue, 19 May 1998, Pete Popov wrote:
> 
> Hi,
> 
> I'm using a mips64 dos-hosted cross
> compiler which I built on my Linux box.
> The compiler has been working fine and
> we haven't ran into any problems, but
> there's something I don't understand and
> it really frustrates me.
> 
> I'm compiling all files with "-nostdinc"
> switch; the files are later linked with
> "-nostdlib".   I've got my own version
> of "memcpy" and a few other routines;
> however, for some reason, the compiler
> chooses to insert the standard libc
> memcpy in some of the files.  Thus, some
> files get my version of memcpy, and
> other get the libc version.  There's is
> no apparent difference in those files;
> they include the same .h files, they are
> compiled with the same switches, etc.
> Any suggestions?

the compiler is not linking in anything from the libc, but it has builtin
functions for some very common functions. when you initialize an
array (or any other datastructure) the compiler needs to have a bcopy or
memcopy. So if the
compiler already has a target-optimized memcpy, why not use it for 
libc memcpy calls as well?
if you do not like this behaviour, turn it off using -fno-builtin

       -fno-builtin
              Don't recognize built-in functions that do not  be-
              gin  with  two leading underscores.  Currently, the
              functions affected include _exit, abort, abs, allo-
              ca,  cos,  exit,  fabs,  labs, memcmp, memcpy, sin,
              sqrt, strcmp, strcpy, and strlen.

              The `-ansi' option prevents alloca and  _exit  from
              being builtin functions.

> 
> Thanks,
> 
> Pete
> 
you're welcome
rolf

+-----------------+-----------------------------------------+
|    _____        |  Rolf Fiedler                           |
|   / ___/        |  Electronic Design Engineer             |
|  / _/           |  Ferrari electronic GmbH                |
| /_/e/r/r/a/r/i/ |  phone: +49 3328 4559 0                 |
|   electronic    |  E-Mail: Rolf.Fiedler@Ferrari.DE        |
|                 |  fax  : +49 3328 4559 60                |
+-----------------+-----------------------------------------+
           "Where do you want to go tomorrow?"

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: GaA0Lt9cAkyY3fgatYUx2tjteW8lyG8I

iQA/AwUANWKTuYCk3bE/FtS8EQL4NQCggaptQ5tuhxpc1+U1KfFTwVGCQxgAoMHQ
hX9QONTl3J1hhlfRX6LjID58
=a2W/
-----END PGP SIGNATURE-----


  parent reply	other threads:[~1998-05-20  6:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-05-19  9:59 No Subject Pete Popov
1998-05-20  6:06 ` memcpy Jonathan Larmour
1998-05-20  6:06 ` Rolf Fiedler [this message]
1998-05-22  9:56 ` Pete Popov
     [not found] <20040316175922.GF14683@qworks.ca>
     [not found] ` <20040316180134.GG14683@qworks.ca>
2004-03-16 18:29   ` your mail Chris Jones
     [not found] <20040223154755.23916.qmail@web41606.mail.yahoo.com>
2004-02-23 16:57 ` Michael Matz
  -- strict thread matches above, loose matches on Subject: below --
1998-09-07  2:33 No Subject Duan, Chenggang (Chenggang)
1998-09-07 15:22 ` your mail joel
1998-09-07 21:04 ` Harry G. Clayton
1998-09-08  8:39   ` joel
1998-04-27 20:39 No Subject Tan Pinghui
1998-04-28  7:12 ` your mail Hans Zuidam

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=Pine.LNX.3.95.980520102050.305A-100000@miraculix.ferrari.de \
    --to=rfie@majestix.ferrari.de \
    --cc=crossgcc@cygnus.com \
    --cc=ppopov@redcreek.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).