public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/58580] New: preprocessor goes OOM with warning for zero literals
Date: Mon, 30 Sep 2013 14:18:00 -0000	[thread overview]
Message-ID: <bug-58580-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 58580
           Summary: preprocessor goes OOM with warning for zero literals
           Product: gcc
           Version: 4.8.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: preprocessor
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rguenth at gcc dot gnu.org

Created attachment 30940
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30940&action=edit
testcase

> g++-4.8  -E test.cpp 
# 1 "test.cpp"
# 1 "<command-line>"
# 1 "test.cpp"
test.cpp:1:1: warning: null character(s) preserved in literal [enabled by
default]
 """""
 ^
test.cpp:2:1: warning: null character(s) preserved in literal [enabled by
default]
""
test.cpp:3:1: warning: null character(s) preserved in literal [enabled by
default]
""
test.cpp:4:1: warning: null character(s) preserved in literal [enabled by
default]
""

cc1plus: out of memory allocating 1677721600 bytes after a total of 405504
bytes

use a suitable ulimit -v to force the error.


             reply	other threads:[~2013-09-30 14:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 14:18 rguenth at gcc dot gnu.org [this message]
2013-09-30 14:20 ` [Bug preprocessor/58580] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2013-10-16  9:51 ` jakub at gcc dot gnu.org
2013-10-21 13:57 ` rguenth at gcc dot gnu.org
2013-10-29 10:17 ` dodji at gcc dot gnu.org
2013-10-31 13:32 ` dodji at gcc dot gnu.org
2013-11-05 14:45 ` rguenth at gcc dot gnu.org
2013-11-06 12:38 ` dodji at gcc dot gnu.org
2013-11-06 17:26 ` [Bug preprocessor/58580] [4.8 " rguenther at suse dot de
2014-01-23  9:13 ` dodji at gcc dot gnu.org
2014-01-27 21:26 ` pthaugen at gcc dot gnu.org
2014-02-24 14:55 ` dodji at gcc dot gnu.org
2014-02-24 14:56 ` rguenth at gcc dot gnu.org
2014-05-22  9:03 ` rguenth at gcc dot gnu.org
2014-12-19 13:32 ` jakub at gcc dot gnu.org
2015-06-23  8:43 ` rguenth 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-58580-4@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).