public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "macdonellba+gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/39142] Compilation fails with specialised optimisations. Date: Mon, 09 Feb 2009 22:54:00 -0000 [thread overview] Message-ID: <20090209225424.939.qmail@sourceware.org> (raw) In-Reply-To: <bug-39142-17287@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from macdonellba+gcc at gmail dot com 2009-02-09 22:54 ------- I'm not really sure that this is worth pursuing for me, since I'm a touch uncertain whether I should expect to have problems with OOM (using over 800MB of RAM once buffers are cleared) on an macro-laden 79KLOC generated C file, albeit with most of the preprocessor directives expanding fairly flatly. If not, I can find another machine to attack the problem of shrinking it with delta, because it's not exactly a task that will be completed within a day. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39142
next prev parent reply other threads:[~2009-02-09 22:54 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-09 18:08 [Bug c/39142] New: " macdonellba+gcc at gmail dot com 2009-02-09 18:10 ` [Bug c/39142] " paolo dot carlini at oracle dot com 2009-02-09 18:13 ` macdonellba+gcc at gmail dot com 2009-02-09 18:15 ` paolo dot carlini at oracle dot com 2009-02-09 22:54 ` macdonellba+gcc at gmail dot com [this message] 2009-02-10 0:35 ` paolo dot carlini at oracle dot com 2009-02-10 10:12 ` [Bug middle-end/39142] " rguenth at gcc dot gnu dot org 2009-02-10 10:21 ` paolo dot carlini at oracle dot com
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=20090209225424.939.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: linkBe 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).