public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.co.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/9100: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault
Date: Wed, 08 Jan 2003 06:46:00 -0000	[thread overview]
Message-ID: <20030108064603.22699.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/9100; it has been noted by GNATS.

From: Neil Booth <neil@daikokuya.co.uk>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, sander_pool@pobox.com, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c/9100: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault
Date: Wed, 8 Jan 2003 06:39:28 +0000

 bangerth@dealii.org wrote:-
 
 > 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.
 
 I'd guess this is an unchecked for "error_mark_node" (death to them), and
 quite easy to fix.
 
 Neil.


             reply	other threads:[~2003-01-08  6:46 UTC|newest]

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

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=20030108064603.22699.qmail@sources.redhat.com \
    --to=neil@daikokuya.co.uk \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).