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: Fri, 22 Aug 2008 11:01:00 -0000 [thread overview]
Message-ID: <48AE205D.C938E9EB@dessent.net> (raw)
In-Reply-To: <D66102A43110FC488698F1C3B605E93108F961C1@exchange01.tanner.com>
Seyran Avanesyan wrote:
> Which version of gcc should I use to compile 64-bit targets.
> I used gcc 3.4.5. With -m64 switch I'm getting this message:
>
> source_file.c:1: sorry, unimplemented: 64-bit mode not compiled in
This is an incomplete question. You need to specify what target you're
talking about. I'm assuming you're referring to the MinGW target. If
that is true, then the MinGW project currently only supports 32 bit
Windows. There is a separate fork of the MinGW project supporting
Windows x64: <http://sourceforge.net/projects/mingw-w64>. This is quite
alpha, as support for Windows x64 in gcc is relatively new and still
under active development.
Brian
next prev parent reply other threads:[~2008-08-22 2:12 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 [this message]
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
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=48AE205D.C938E9EB@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).