public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Fulton.Green@Retek.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/10249: -gxcoff switch causes parser to abort
Date: Thu, 27 Mar 2003 22:56:00 -0000	[thread overview]
Message-ID: <20030327223044.15963.qmail@sources.redhat.com> (raw)


>Number:         10249
>Category:       c++
>Synopsis:       -gxcoff switch causes parser to abort
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Thu Mar 27 22:36:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Fulton.Green@Retek.com
>Release:        3.3 20030324 (prerelease)
>Organization:
>Environment:
Chipset: PowerPC 603e
Make:    IBM
Model:   F40
OS:      AIX 4.3
>Description:
Invoking the C++ front-end, specifying XCOFF object output, on a source file containing a simple base class and subclass declaration:

   $(GCC_HOME)/lib/$(PLATFORM)/$(VERSION)/cc1plus -gxcoff How-To-Repeat.ii

generates the following message:

   <stdin>:7: internal compiler error: in tree_low_cst, at tree.c:3228

The referenced tree.c is in $GCCSRC/gcc, NOT $GCCSRC/gcc/cp.

The ICE disappears if the -gxcoff switch is removed.
>How-To-Repeat:
// filename: How-To-Repeat.ii
// a simple base class and subclass declaration
//
// compile with -gxcoff (assuming the compiler has
// support for it) to reproduce the problem

class BaseClass
{
   int x;
};

class Subclass : public BaseClass
{
  int y;
};
>Fix:
Choose one:
- don't declare subclasses
- don't use the -gxcoff switch
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-03-27 22:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030327223044.15963.qmail@sources.redhat.com \
    --to=fulton.green@retek.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).