This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: 64-bit gcc

From: NightStrike <nightstrike at gmail dot com>
To: gcc-help at gcc dot gnu dot org
Cc: "Seyran Avanesyan" <seyran dot avanesyan at tanner dot com>
Date: Fri, 22 Aug 2008 22:44:55 -0400
Subject: Re: 64-bit gcc
References: <d85a51ff0808190837n3a30ab98ld21257f1471f499d@mail.gmail.com> <200808191257.28899.zepm@gatech.edu> <D66102A43110FC488698F1C3B605E93108F961C1@exchange01.tanner.com> <48AE205D.C938E9EB@dessent.net> <D66102A43110FC488698F1C3B605E93108F9624F@exchange01.tanner.com> <48AF1CC0.4FC8BBC1@dessent.net> <D66102A43110FC488698F1C3B605E93108F96292@exchange01.tanner.com> <48AF74C9.90FCDEF6@dessent.net>

On 8/22/08, Brian Dessent <brian@dessent.net> wrote:
> 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.

Correct, we don't have any.  We push everything upstream.

References:
- Restricting symbol binding within shared object
  - From: Arindam
- special comments handling in the C compiler
  - From: Tim Wang
- 64-bit gcc
  - From: Seyran Avanesyan
- Re: 64-bit gcc
  - From: Brian Dessent
- RE: 64-bit gcc
  - From: Seyran Avanesyan
- Re: 64-bit gcc
  - From: Brian Dessent
- RE: 64-bit gcc
  - From: Seyran Avanesyan
- Re: 64-bit gcc
  - From: Brian Dessent

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]