public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: ali hagigat <hagigatali@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: suggestion for GCC (1)
Date: Wed, 09 Feb 2011 10:26:00 -0000	[thread overview]
Message-ID: <mcrsjvxptwv.fsf@google.com> (raw)
In-Reply-To: <AANLkTikKk+uyrWQSoT3p74c31TTaSNzCgq2uLa5++X+=@mail.gmail.com>	(ali hagigat's message of "Wed, 9 Feb 2011 09:33:16 +0330")

ali hagigat <hagigatali@gmail.com> writes:

> Are memcmp, memset, and memmove built in?
> So a built in function may be in the library or the code I write. right?

Yes.

> I have used cross compilers for micro controllers for years. They
> translate C/Assembly code you write and produce a final object file.
> they are not dependent on operating system, system calls or force our
> code to be linked with some unknown strange libraries which programmer
> does not know about them at all.
>
> How they work? Professionals like you can implement the same
> functionality for gcc without the weak point of adding mem functions.
>
> It is an idea but I am surprised how you say that it is impossible to
> do such a thing.

I don't think that I said that it is impossible to do such a thing.  If
I did, I misspoke, and I apologize for that if in fact I did do it.

I think that, rather than saying that doing something else is
impossible, I explained why gcc acts the way it does.

> Besides gcc is dependent to what? operating system or the architecture
> of hardware like Intel chipsets, host bridge and I/O bridge in
> addition to CPU?

As you know, gcc is generally independent of the host bridge and I/O
bridge.  It is of course dependent on the CPU itself.  It is dependent
on the target operating system in a few ways.

Ian

  reply	other threads:[~2011-02-09  7:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2011-02-09 15:23       ` David Brown
2011-03-06 13:19         ` Enrico Weigelt
2011-02-09  7:08     ` Ian Lance Taylor
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=mcrsjvxptwv.fsf@google.com \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=hagigatali@gmail.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).