public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55287] GCC crashes and asks to file bug report
Date: Tue, 13 Nov 2012 12:01:00 -0000 [thread overview]
Message-ID: <bug-55287-4-aKCoQQh6tH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55287-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #6 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-11-13 11:59:48 UTC ---
(In reply to comment #4)
> Why is GCC comsuming so much memory?
>
> The program has 6.4MB source code, it is a single function. All optimizations
> are turned off. And there is 2GB memory in the system.
>
> Well, shouldn't it be possible to compile this program?
That depends on the program, where the memory goes, possible bugs, etc.
To start investigating this, GCC devs would need the info requested here:
http://gcc.gnu.org/bugs/#report
That said, even if you provided that info, it is unlikely that anyone will look
into this bug, since it is a unusual case. If adding 2 or 4 more GBs of memory
(or splitting the function into many small pieces) solves the issue, then it is
simpler to just do that, and focus on fixing other bugs.
Of course, nothing prevents you from investigating the issue yourself. Perhaps
you are able to uncover a clear bug, memory leak or potential improvement. See:
http://gcc.gnu.org/wiki/Speedup_areas
http://gcc.gnu.org/wiki/Memory_management
http://gcc.gnu.org/wiki/PerformanceTesting
prev parent reply other threads:[~2012-11-13 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 15:18 [Bug c++/55287] New: " gordoncichon at gmail dot com
2012-11-12 15:22 ` [Bug c++/55287] " paolo.carlini at oracle dot com
2012-11-12 17:02 ` pinskia at gcc dot gnu.org
2012-11-12 17:50 ` paolo.carlini at oracle dot com
2012-11-13 8:33 ` gordoncichon at gmail dot com
2012-11-13 9:44 ` redi at gcc dot gnu.org
2012-11-13 12:01 ` manu at gcc dot gnu.org [this message]
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=bug-55287-4-aKCoQQh6tH@http.gcc.gnu.org/bugzilla/ \
--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).