From: Andrew Haley <aph@redhat.com>
To: mahmoodn <nt_mahmood@yahoo.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: cc1plus take too much memory
Date: Mon, 31 Dec 2007 11:16:00 -0000 [thread overview]
Message-ID: <18296.53113.311195.703501@zebedee.pink> (raw)
In-Reply-To: <14554622.post@talk.nabble.com>
mahmoodn writes:
>
> >Run the program you were trying to compile through "gcc -E". How big
> >is the resulting text? Are there any particularly long functions in
> >your program? That kind of thing.
>
> I have long functions with many typedefs. Have they any effect?
>
> in the directory than contain makefile, the result of "gcc -E" is:
> [naderan@Milky-way VVc_diagram_2]$ gcc -E
> gcc: no input files
>
> I use "make" instead to compile the project. what should I do then?
Compile whichever file is causing the trouble with gcc -E to extract
the preprocessed source.
Have you ever compiled a C file without using make?
Andrew.
--
Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, UK
Registered in England and Wales No. 3798903
next prev parent reply other threads:[~2007-12-31 11:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 13:05 mahmoodn
2007-12-30 13:18 ` Andrew Haley
2007-12-30 17:28 ` mahmoodn
2007-12-30 20:31 ` Andrew Haley
2007-12-31 6:04 ` mahmoodn
2007-12-31 11:16 ` Andrew Haley [this message]
2008-01-01 10:29 ` mahmoodn
2008-01-01 13:16 ` Andrew Haley
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=18296.53113.311195.703501@zebedee.pink \
--to=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=nt_mahmood@yahoo.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).