From: Ian Lance Taylor <iant@google.com>
To: Michael Witten <mfwitten@MIT.EDU>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Tiny GCC: Pure, Unadulterated, Object Code
Date: Wed, 30 Jan 2008 10:20:00 -0000 [thread overview]
Message-ID: <m38x28wrsm.fsf@localhost.localdomain> (raw)
In-Reply-To: <2CDFCA36-07C2-4871-8773-15F2DAD35DEB@MIT.EDU>
Michael Witten <mfwitten@MIT.EDU> writes:
> > There is just no way to make a "generic i386 gcc".
>
> Sure there is: Pure binary.
That makes no sense in the context you are discussing. There is no
pure binary which will run on both a GNU/Linux system and a Windows
system. Even on a bare embedded board, which is very different from a
GNU/Linux or Windows system, different devices must be handled in
different ways.
I think you need to understand why this makes no sense before you can
proceed to understanding why the rest of your posting makes no sense.
Ian
next prev parent reply other threads:[~2008-01-29 15:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 12:21 Michael Witten
2008-01-24 14:29 ` Ian Lance Taylor
2008-01-25 4:23 ` Brian Dessent
2008-01-26 2:47 ` Michael Witten
2008-01-26 16:17 ` [Progress] " Michael Witten
2008-01-26 22:16 ` Michael Witten
2008-01-28 0:46 ` Andrew Haley
2008-01-27 13:07 ` Michael Witten
2008-01-27 8:45 ` Brian Dessent
2008-01-29 1:36 ` Scott Moore
2008-01-29 15:55 ` Michael Witten
2008-01-29 16:56 ` Brian Dessent
2008-01-29 18:16 ` Michael Witten
2008-01-29 18:36 ` Brian Dessent
2008-01-29 20:31 ` Michael Witten
2008-01-30 1:14 ` NightStrike
2008-01-30 7:09 ` Michael Witten
2008-01-30 10:20 ` Ian Lance Taylor [this message]
2008-01-30 10:54 ` Michael Witten
2008-01-30 12:09 ` Ian Lance Taylor
2008-01-29 14:22 ` John Carter
2008-01-29 15:40 ` Michael Witten
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=m38x28wrsm.fsf@localhost.localdomain \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=mfwitten@MIT.EDU \
/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).