From: Thomas Dineen <tdineen@ix.netcom.com>
To: gcc-help@gcc.gnu.org, Thomas Dineen <tdineen@ix.netcom.com>
Subject: Gcc Error
Date: Sat, 22 Aug 2015 06:19:00 -0000 [thread overview]
Message-ID: <55D81472.40200@ix.netcom.com> (raw)
Gentle People:
When Building a rather large project gcc produces the following error:
"Out of memory for code representation:" See the details below.
What is the best or simplest way to fix this?
1) Will using 64 bit via the -m64 flag fix this?
or
2) I am currently building the project with single gcc call. (The slow way)
Due to some legacy issues with GTK/Cairo and extern variables one big build
seems to work. Would it be better to compile each .C File to a .O file
and then
link (Faster way).
3) I am using an older gcc 3.4.6 on Solaris 10. Would a simple update to
a newer
version solve the out of memory problem shown above. (Separate from the -m64
issue shown below)?
Sun5# !ma
make TA_Benchs
Running Target: TA_Bench Sun
gcc -D_REENTRANT -ggdb -w -g -c IB_TWS_API.c Read_IB_Callbacks.c
gcc Main.c -ggdb -w IB_TWS_API.o Read_IB_Callbacks.o `pkg-config
--cflags --libs gtk+-2.0 ` -lcurl -lm -lsocket -lnsl -ggdb -w -o
TA_Bench.sun
Assembler: Main.c
"/var/tmp//ccVeiKcL.s", line 15324105 : Out of memory for code
representation
make: *** [TA_Benchs] Error 1
Sun5# !ma
make TA_Benchs
make: Warning: File `Makefile' has modification time 847 s in the future
Running Target: TA_Bench Sun
gcc -m64 -D_REENTRANT -ggdb -w -g -c IB_TWS_API.c Read_IB_Callbacks.c
IB_TWS_API.c:1: sorry, unimplemented: 64-bit mode not compiled in
Read_IB_Callbacks.c:1: sorry, unimplemented: 64-bit mode not compiled in
make: *** [TA_Benchs] Error 1
Sun5# gcc --version
gcc (GCC) 3.4.6
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
next reply other threads:[~2015-08-22 6:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-22 6:19 Thomas Dineen [this message]
2015-08-22 8:46 ` Jonathan Wakely
2015-08-23 0:07 ` Thomas Dineen
2015-08-23 14:01 ` Jonathan Wakely
-- strict thread matches above, loose matches on Subject: below --
2008-11-16 21:17 GCC Error Denisius
2008-11-17 9:04 ` Ian Lance Taylor
2008-12-26 18:41 ` fimer
2008-12-26 18:44 ` Jan Engelhardt
2008-12-28 4:27 ` Ian Lance Taylor
[not found] <20040417113541.24299.qmail@gossamer.airs.com>
2004-04-17 14:37 ` GCC error Ian Lance Taylor
2004-04-17 11:35 anissi
2004-04-17 11:35 anissi
[not found] <616BE6A276E3714788D2AC35C40CD18D7404AF@whale.softwire.co.uk>
2002-07-29 7:02 ` gcc error Rupert Wood
2002-08-10 5:32 ` Nix
2002-07-29 5:12 Linux
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=55D81472.40200@ix.netcom.com \
--to=tdineen@ix.netcom.com \
--cc=gcc-help@gcc.gnu.org \
/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).