public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	sander_pool@pobox.com
Subject: Re: c/9100: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault
Date: Wed, 08 Jan 2003 01:19:00 -0000	[thread overview]
Message-ID: <20030108011950.22354.qmail@sources.redhat.com> (raw)

Old Synopsis: illegal binary constant causes gcc to seg fault
New Synopsis: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Tue Jan  7 17:19:50 2003
State-Changed-Why:
    A minimal testcase is this (just this one line):
    -------------------------
    int i = (0b11111000 == 0);
    -------------------------
    It crashes both the C and C++ front ends with a SegFault.
    This is a regression from gcc3.2 that happens both on
    the 3.3 branch as well as on the mainline. It also happens
    on x86-Linux, not only the win-x-avr crosscompiler for which
    the report initially was.
    
    W.
    
    The crash for me:
    tmp/g> /home/bangerth/bin/gcc-3.3-pre/bin/gcc x.c
    x.c:1:9: invalid suffix "b11111000" on integer constant
    x.c:1: internal compiler error: Segmentation fault
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9100


             reply	other threads:[~2003-01-08  1:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08  1:19 bangerth [this message]
2003-01-08  6:46 Neil Booth
2003-02-08 16:43 ebotcazou
2003-02-11 22:57 ebotcazou

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=20030108011950.22354.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=sander_pool@pobox.com \
    /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).