public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "falk at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/12440] gcc 3.3.1 on i386 linux 2.4.22 crashes during compilation of quicktime4linux 2.0.0
Date: Mon, 29 Sep 2003 09:42:00 -0000	[thread overview]
Message-ID: <20030929085756.23985.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030929084127.12440.fritz@reichmann.tv>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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



------- Additional Comments From falk at debian dot org  2003-09-29 08:57 -------
Out of memory problem. To me, it looks like the test case is simply too large
to be compiled with full optimization and inlining. I don't think there's much we 
can do about that, but I'll leave it open for now, maybe somebody else finds
something particularly memory-eating in this test case.


  parent reply	other threads:[~2003-09-29  8:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29  8:48 [Bug c/12440] New: " fritz at reichmann dot tv
2003-09-29  8:49 ` [Bug c/12440] " fritz at reichmann dot tv
2003-09-29  8:52 ` fritz at reichmann dot tv
2003-09-29  8:57 ` fritz at reichmann dot tv
2003-09-29  8:58 ` fritz at reichmann dot tv
2003-09-29  9:00 ` fritz at reichmann dot tv
2003-09-29  9:08 ` fritz at reichmann dot tv
2003-09-29  9:42 ` falk at debian dot org [this message]
2003-09-29  9:56 ` fritz at reichmann dot tv
2003-09-29 10:34 ` fritz at reichmann dot tv
2003-10-02 18:07 ` [Bug optimization/12440] " pinskia at gcc dot gnu dot org
2004-01-02  4:03 ` pinskia at gcc dot gnu dot org
2004-01-02  4:08 ` pinskia at gcc dot gnu dot org
2004-01-02  4:09 ` [Bug optimization/12440] [3.3/3.4 Regression] " pinskia at gcc dot gnu dot org
2004-01-02  4:10 ` pinskia at gcc dot gnu dot org
2004-01-10 19:41 ` pinskia at gcc dot gnu dot org
2004-01-10 23:07 ` rakdver at atrey dot karlin dot mff dot cuni dot cz
2004-01-14  3:44 ` pinskia at gcc dot gnu dot org
2004-01-20 16:56 ` [Bug optimization/12440] [3.3/3.4/3.5 " cvs-commit at gcc dot gnu dot org
2004-01-20 17:13 ` [Bug optimization/12440] [3.3/3.4 " pinskia at gcc dot gnu dot org
2004-01-24 11:19 ` cvs-commit at gcc dot gnu dot org
2004-01-24 15:16 ` [Bug optimization/12440] [3.3 " pinskia at gcc dot gnu dot org
2004-01-27 13:05 ` cvs-commit at gcc dot gnu dot org
2004-01-29  4:42 ` cvs-commit at gcc dot gnu dot org
2004-01-29  4:43 ` gdr 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=20030929085756.23985.qmail@sources.redhat.com \
    --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).