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: "Seyran Avanesyan" <seyran dot avanesyan at tanner dot com>
Cc: brian at dessent dot net, gcc-help at gcc dot gnu dot org
Date: Fri, 22 Aug 2008 21:59:32 -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>

On 8/22/08, Seyran Avanesyan <seyran.avanesyan@tanner.com> wrote:
> Thanks for reply.
>
> 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.

The mingw-w64 project that Brian linked you to can generate 32-bit as
well as 64-bit binaries.  You can cross compile from 5 different
systems, or you can compile natively.

The current version is stable enough to compile several
high-visibility projects, including wxwidgets, vlc, ffmpeg, and more.
If you need help with anything, post on the mailing list or forum for
that project.

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]