public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub 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: Tue, 29 May 2012 07:46:00 -0000 [thread overview] Message-ID: <bug-53510-4-8TVIAF3srV@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2012-05-29 AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org |gnu.org | Ever Confirmed|0 |1 --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-05-29 07:30:28 UTC --- Created attachment 27515 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27515 gcc48-pr53510.patch Ugh, that leaks like crazy. Not only it forgets to free buffers, but also doubles the size of the allocation (which is fine) but only adds 2 to the expected allocated block length, so it allocates twice as much for every 2 bytes beyond 200 characters on a line.
next prev parent reply other threads:[~2012-05-29 7:30 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 ` [Bug middle-end/53510] [4.8 Regression] " pinskia at gcc dot gnu.org 2012-05-28 17:30 ` 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 [this message] 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-8TVIAF3srV@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: 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).