public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paul@parasoft.com
To: gcc-gnats@gcc.gnu.org
Cc: sang@parasoft.com, leif@parasoft.com
Subject: c++/2540: Internal compiler error in `push_decl_scope', at dwarf2out.c:7726
Date: Wed, 11 Apr 2001 16:26:00 -0000	[thread overview]
Message-ID: <20010411232026.9439.qmail@sourceware.cygnus.com> (raw)

>Number:         2540
>Category:       c++
>Synopsis:       Internal compiler error in `push_decl_scope', at dwarf2out.c:7726
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 11 16:26:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     paul@parasoft.com
>Release:        gcc-2.95.2 and gcc-2.95.3 (but not egcs-2.91.66)
>Organization:
>Environment:
Irix 6.5
>Description:
compiling test case with '-g' causes 
internal compiler error
>How-To-Repeat:
/usr/local/gcc-2.95.3/bin/g++ -c -g junk.cc
junk.cc:23: Internal compiler error in `push_decl_scope', at dwarf2out.c:7726
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/plain; name="junk.cc"
Content-Disposition: inline; filename="junk.cc"

struct Insure {
    class Object;
    class BadFormatBug;
    class Resources;
};
class Insure::Object {
public:
    static int roundUp(int, int);
    static inline char *roundUp(char *ptr, int align) {
        return (char *)0 + roundUp(ptr - (char *)0, align);
    }
};
class Insure::BadFormatBug {
public:
    enum ExprCode {
        BF_ERROR,
    };
};
class Insure::Resources {
public:
    virtual const char *badFormatExprFormat(BadFormatBug::ExprCode exprCode);
};


             reply	other threads:[~2001-04-11 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-11 16:26 paul [this message]
2001-08-12 11:23 rodrigc
2001-11-15 13:06 rodrigc
2001-11-15 13:31 rodrigc

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=20010411232026.9439.qmail@sourceware.cygnus.com \
    --to=paul@parasoft.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=leif@parasoft.com \
    --cc=sang@parasoft.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).