public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/53510] [4.8 Regression] OOM while compile some code
Date: Mon, 28 May 2012 17:29:00 -0000	[thread overview]
Message-ID: <bug-53510-4-2zscooM2L6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53510-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |diagnostic, memory-hog
          Component|c++                         |middle-end
   Target Milestone|---                         |4.8.0
            Summary|OOM while compile some code |[4.8 Regression] OOM while
                   |                            |compile some code

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-05-28 17:21:05 UTC ---
#1  0x0000000000f7b7ea in read_line (file=0x18d9b50) at
/home/pinskia/src/local/gcc/gcc/input.c:111
111          memcpy (ptr, string, pos);
(gdb) p pos
$2 = 96889
(gdb) p/x pos
$3 = 0x17a79

So this is the error message which is causing the huge memory usage.


  parent reply	other threads:[~2012-05-28 17:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-28 17:16 [Bug c++/53510] New: " pinskia at gcc dot gnu.org
2012-05-28 17:17 ` [Bug c++/53510] " pinskia at gcc dot gnu.org
2012-05-28 17:29 ` pinskia at gcc dot gnu.org [this message]
2012-05-28 17:30 ` [Bug middle-end/53510] [4.8 Regression] " paolo.carlini at oracle dot com
2012-05-28 17:38 ` pinskia at gcc dot gnu.org
2012-05-28 17:44 ` paolo.carlini at oracle dot com
2012-05-29  7:46 ` jakub at gcc dot gnu.org
2012-05-29  8:05 ` manu at gcc dot gnu.org
2012-05-29 11:53 ` jakub at gcc dot gnu.org
2012-05-31 12:17 ` jakub at gcc dot gnu.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=bug-53510-4-2zscooM2L6@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).