public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: ali hagigat <hagigatali@gmail.com>
To: Kai Ruottu <kai.ruottu@wippies.com>, gcc-help@gcc.gnu.org
Subject: Re: suggestion for GCC (1)
Date: Mon, 07 Feb 2011 11:03:00 -0000	[thread overview]
Message-ID: <AANLkTi=KEnLVjGedpbO4bS8brhNBHRB7Zaa6N_+TW8RS@mail.gmail.com> (raw)
In-Reply-To: <4D4FC8E0.5080306@wippies.com>

Dear Kai,

If I can compile a C/assembly program without linking with standard
libraries by using -nostdlib, so why the manual of gcc says:
-------------------------------------------
Do not use the standard system startup files or libraries when
linking.  No startup files and only the libraries you specify will be
passed to the linker.  The compiler may generate calls to "memcmp",
"memset", "memcpy" and "memmove".
-------------------------------------------
So the compiler still calls "memcmp", "memset", "memcpy" and
"memmove".  While my code does not have them!!
Regards

On Mon, Feb 7, 2011 at 1:56 PM, Kai Ruottu <kai.ruottu@wippies.com> wrote:
> Oops, of course this will succed for ANY target!  Getting at least
> 'libgcc' for the embedded targets then has always been possible!

  parent reply	other threads:[~2011-02-07 10:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 10:23 ali hagigat
2011-02-07 10:26 ` Kai Ruottu
2011-02-07 10:29   ` Kai Ruottu
2011-02-07 10:57     ` ali hagigat
2011-02-07 11:03     ` ali hagigat [this message]
2011-02-07 23:43 ` Ian Lance Taylor
2011-02-08  0:44   ` Thomas Martitz
2011-02-08  7:35     ` Ian Lance Taylor
2011-02-08 14:23       ` David Brown
2011-02-09  4:54         ` Ian Lance Taylor
2011-02-09  5:17 ali hagigat
2011-02-09  5:27 ` Ian Lance Taylor
2011-02-09  6:03   ` ali hagigat
2011-02-09  7:05     ` ali hagigat
2011-02-09 10:26       ` Ian Lance Taylor
2011-02-09 15:23       ` David Brown
2011-03-06 13:19         ` Enrico Weigelt
2011-02-09  7:08     ` Ian Lance Taylor

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='AANLkTi=KEnLVjGedpbO4bS8brhNBHRB7Zaa6N_+TW8RS@mail.gmail.com' \
    --to=hagigatali@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=kai.ruottu@wippies.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).