public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/58580] [4.8 Regression] preprocessor goes OOM with warning for zero literals
Date: Mon, 27 Jan 2014 21:26:00 -0000	[thread overview]
Message-ID: <bug-58580-4-1Y2EOiqCqy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58580-4@http.gcc.gnu.org/bugzilla/>

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

Pat Haugen <pthaugen at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pthaugen at gcc dot gnu.org

--- Comment #11 from Pat Haugen <pthaugen at gcc dot gnu.org> ---
CPU2000 benchmark 253.perlbmk started failing to build for me starting with
revision 206957. Reduced down to following example.

[pthaugen@igoo 00000001]$ cat junk.c
# define HAS_FGETPOS
[pthaugen@igoo 00000001]$ /home/pthaugen/install/gcc/gcc_hunt/bin/gcc -c junk.c
-DHAS_FGETPOS
junk.c:1:0: warning: "HAS_FGETPOS" redefined [enabled by default]
 # define HAS_FGETPOS
 ^
<command-line>:0:0: note: this is the location of the previous definition
junk.c:1:0: internal compiler error: Segmentation fault
 # define HAS_FGETPOS
 ^
0x10667507 crash_signal
    /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/toplev.c:337
0x10cab5b7 add_file_to_cache_tab
    /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/input.c:296
0x10cab5b7 lookup_or_add_file_to_cache_tab
    /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/input.c:330
0x10cab5b7 location_get_source_line(expanded_location, int*)
    /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/input.c:704
0x10ca5167 diagnostic_show_locus(diagnostic_context*, diagnostic_info const*)
    /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/diagnostic.c:304
0x10ca580b diagnostic_report_diagnostic(diagnostic_context*, diagnostic_info*)
    /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/diagnostic.c:800
0x10156397 c_cpp_error(cpp_reader*, int, int, unsigned int, unsigned int, char
const*, char**)
    /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/c-family/c-common.c:9638
0x10cb85af cpp_diagnostic_with_line
    /home/pthaugen/src/gcc/gcc_hunt/gcc/libcpp/errors.c:145
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.


  parent reply	other threads:[~2014-01-27 21:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 14:18 [Bug preprocessor/58580] New: " rguenth at gcc dot gnu.org
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 [this message]
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-1Y2EOiqCqy@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).