public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: mahmoodn <nt_mahmood@yahoo.com>
To: gcc-help@gcc.gnu.org
Subject: Re: cc1plus take too much memory
Date: Sun, 30 Dec 2007 17:28:00 -0000	[thread overview]
Message-ID: <14549096.post@talk.nabble.com> (raw)
In-Reply-To: <18295.39564.699467.564027@zebedee.pink>


>  gcc 3.3 (released May 2003) is no longer being developed.  Anything
>  it does today it will always do.

I will work around with my code to get it ready for newer versions of gcc,
but untill then:

>  We don't know if this is abnormal because we don't know what you
>  were trying to compile.

what information should I provide?




Andrew Haley wrote:
> 
> mahmoodn writes:
>  > 
>  > I do not know why gcc process (cc1plus) take too much memory during
>  > compilation (over 600 MB). according to system monitor, 
>  > 
>  > total:      658 MB
>  > RSS:     651 MB
>  > shared:  11.2 MB
>  > 
>  > Don't you think it is abnormal?>-( maybe there is a memory leak in gcc. 
>  > 
>  > I have to say that I use gcc 3.3
> 
> A couple of things:
> 
>   gcc 3.3 (released May 2003) is no longer being developed.  Anything
>   it does today it will always do.
> 
>   We don't know if this is abnormal because we don't know what you
>   were trying to compile.
> 
> Andrew.
> 
> -- 
> Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor,
> Berkshire, SL4 1TE, UK
> Registered in England and Wales No. 3798903
> 
> 

-- 
View this message in context: http://www.nabble.com/cc1plus-take-too-much-memory-tp14547002p14549096.html
Sent from the gcc - Help mailing list archive at Nabble.com.

  reply	other threads:[~2007-12-30 17:28 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 [this message]
2007-12-30 20:31     ` Andrew Haley
2007-12-31  6:04       ` mahmoodn
2007-12-31 11:16         ` Andrew Haley
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=14549096.post@talk.nabble.com \
    --to=nt_mahmood@yahoo.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).