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: Brian Dessent <brian at dessent dot net>
To: Seyran Avanesyan <seyran dot avanesyan at tanner dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Fri, 22 Aug 2008 13:08:32 -0700
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>
Reply-to: gcc-help at gcc dot gnu dot org

Seyran Avanesyan wrote:

> Yes, the target was Windows, and the separate fork is in active
> development, this is why I was looking for earlier versions.
> According to some posts gcc3.2.0 should do that. But it isn't, so I was
> wondering if instead of downloading binaries I might have to compile
> GCC/MinGW myself to get that working.

x86_64 support for *Linux* was in gcc 3.2.  Not Windows x64.  They are
very different targets even though the underlying hardware might be the
same.

> And I'm also interested in compiling 64-bit targets using original GCC
> (planning to move Linux soon).

What do you mean by "original gcc"? 

Brian

Follow-Ups:
- RE: 64-bit gcc
  - From: Seyran Avanesyan

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

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