public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/18936] GCC gives internal error and uses all sytem ram before doing so.
Date: Mon, 27 Dec 2004 01:04:00 -0000	[thread overview]
Message-ID: <20041227010405.14673.qmail@sourceware.org> (raw)
In-Reply-To: <20041211003627.18936.belgarath@pimpsoft.com>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-12-27 01:04 -------
(In reply to comment #3)
> Subject: Re:  GCC gives internal error and uses all sytem ram before doing so.
> 
> I told you where to get the source. 
But that does not help us here because your system headers might be different than what the developer 
is using and might not notice the memory problem.  Read <http://gcc.gnu.org/bugs.html> as 
requested and attach the preprocessed source.  It is not very hard to get the preprocessed source, just 
add -save-temps and then attach the cmu_us_kal16_diphone.i file as it will save it.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|critical                    |normal
           Keywords|                            |memory-hog


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18936


  parent reply	other threads:[~2004-12-27  1:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041211003627.18936.belgarath@pimpsoft.com>
2004-12-20 12:27 ` christian dot joensson at gmail dot com
2004-12-20 13:09 ` falk at debian dot org
2004-12-27  1:04 ` pinskia at gcc dot gnu dot org [this message]
2005-03-29 18:56 ` [Bug other/18936] " ebotcazou at gcc dot gnu dot org

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=20041227010405.14673.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).