public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
To: Seyran Avanesyan <seyran.avanesyan@tanner.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: 64-bit gcc
Date: Sat, 23 Aug 2008 02:31:00 -0000	[thread overview]
Message-ID: <48AF74C9.90FCDEF6@dessent.net> (raw)
In-Reply-To: <D66102A43110FC488698F1C3B605E93108F96292@exchange01.tanner.com>

Seyran Avanesyan wrote:

> > What do you mean by "original gcc"?
> 
> By "original gcc" I meant not the one in MinGW (or any other ports of
> GCC). My understanding is that GCC was created for Linux/Unix systems in
> first place.

You're making a distinction where one does not exist.  gcc is gcc.  gcc
currently supports something like three dozen architectures, all from a
single code base.  (And if you count OS variations[1] and bare metal
systems the number of distinct targets is in the hundreds.)  There is no
"linux gcc version" or "windows gcc version", it's all the same codebase
built with different options or in different environments.

Some ports might have some local patches that are not in FSF gcc (but I
don't think mingw-w64 has any) but those are usually to correct broken
behavior in certain corner cases so they are things you want.

Brian

[1] For example, for the x86 architecture alone: Linux, Darwin/OS X,
Cygwin, MinGW, {Free,Net,Open}BSD, RTEMS, Vxworks, bare metal, etc.

  reply	other threads:[~2008-08-23  2:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 16:12 Restricting symbol binding within shared object Arindam
2008-08-19 16:58 ` special comments handling in the C compiler Tim Wang
2008-08-22  1:52   ` extern "C" From command line Seyran Avanesyan
2008-08-22  2:12     ` Brian Dessent
2008-08-23  1:38       ` Seyran Avanesyan
2008-08-23  2:37         ` Brian Dessent
2008-08-23  2:46           ` Seyran Avanesyan
2008-08-22  2:04   ` 64-bit gcc Seyran Avanesyan
2008-08-22 11:01     ` Brian Dessent
2008-08-22 20:09       ` Seyran Avanesyan
2008-08-22 22:32         ` Brian Dessent
2008-08-22 22:45           ` Seyran Avanesyan
2008-08-23  2:31             ` Brian Dessent [this message]
2008-08-23  2:45               ` NightStrike
2008-08-23  2:49               ` Seyran Avanesyan
2008-08-23  3:18                 ` Brian Dessent
2008-08-23  2:00         ` NightStrike
2008-08-23  2:13           ` Seyran Avanesyan
2008-08-19 18:49 ` Restricting symbol binding within shared object Ian Lance Taylor
2008-08-20 19:36   ` Arindam
2008-08-21  4:43     ` 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=48AF74C9.90FCDEF6@dessent.net \
    --to=brian@dessent.net \
    --cc=gcc-help@gcc.gnu.org \
    --cc=seyran.avanesyan@tanner.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).