public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: warwick@trolltech.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/10853: Parse internal error on ambiguous syntax.
Date: Mon, 19 May 2003 07:56:00 -0000	[thread overview]
Message-ID: <20030519075420.18192.qmail@sources.redhat.com> (raw)


>Number:         10853
>Category:       c++
>Synopsis:       Parse internal error on ambiguous syntax.
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon May 19 07:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     warwick@trolltech.com
>Release:        3.2
>Organization:
>Environment:
i486-suse-linux
>Description:
Small attached file gives internal compiler error (new in 3.2):

ambigsyntaxcrash.cpp: In function `void func()':
ambigsyntaxcrash.cpp:12: type specifier omitted for parameter `
Internal compiler error: Error reporting routines re-entered.
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>How-To-Repeat:
gcc ambigsyntaxcrash.cpp
>Fix:
Disambiguate syntax (eg. "int(d)" becomes "(int)(d)").
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-c++src; name="ambigsyntaxcrash.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="ambigsyntaxcrash.cpp"

Y2xhc3MgVHlwZSB7CnB1YmxpYzoKICAgIFR5cGUoaW50LGludCk7Cn07Cgp2b2lkIGZ1bmMoKQp7
CiAgICBkb3VibGUgZDsKICAgIGludCBpKCk7CgogICAgLy8gT0sgdG8gZ2V0IGNvbmZ1c2VkICg/
KSwgbm90IE9LIHRvICJpbnRlcm5hbCBjb21waWxlciBlcnJvciIKICAgIFR5cGUgdmFyKChpbnQp
KGQpLCBpKCkpOwp9Cg==


             reply	other threads:[~2003-05-19  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-19  7:56 warwick [this message]
2003-05-19  8:37 giovannibajo

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=20030519075420.18192.qmail@sources.redhat.com \
    --to=warwick@trolltech.com \
    --cc=gcc-gnats@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).