public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: niemayer@isg.de
To: gcc-gnats@gcc.gnu.org
Subject: c++/3543: gcc-3.0 Internal error #56 in resolve_offset_ref, at cp/init.c:1963
Date: Tue, 03 Jul 2001 06:56:00 -0000	[thread overview]
Message-ID: <20010703134731.31308.qmail@sourceware.cygnus.com> (raw)

>Number:         3543
>Category:       c++
>Synopsis:       gcc-3.0 Internal error #56 in resolve_offset_ref, at cp/init.c:1963
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Tue Jul 03 06:56:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Peter Niemayer
>Release:        gcc version 3.0
>Organization:
>Environment:
i686-pc-linux-gnu
>Description:
When compiling the attached test-case source:

> gcc -O3 -c ise_56.cxx 
ise_56.cxx: In member function `virtual long unsigned int Pipe::ewrite(const 
   void*, long unsigned int)':
ise_56.cxx:55: Internal error #56.
ise_56.cxx:55: Internal compiler error in resolve_offset_ref, at cp/init.c:1963

The same small test source compiled with "-O2" instead of
"-O3" works fine, so I assume the new inliner is the cause
of the problem.
>How-To-Repeat:

>Fix:
small rearrangements of the code let the bug disappear,
e.g. replacing

(Writeable::blocking_mode)

by 

(Writeable::blocking_mode == true)

That of course is an ugly workaround, only... :-)
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="ise_56.cxx"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="ise_56.cxx"

CmNsYXNzIFJlYWRhYmxlIHsKcHJvdGVjdGVkOgogICAgICAgIGJvb2wgYmxvY2tpbmdfbW9kZTsK
CnB1YmxpYzoKICAgICAgICBSZWFkYWJsZSh2b2lkKSA6IGJsb2NraW5nX21vZGUodHJ1ZSkgeyB9
OwogICAgICAgIHZpcnR1YWwgflJlYWRhYmxlKHZvaWQpIHsgfTsKCn07CgpjbGFzcyBXcml0ZWFi
bGUgewpwcm90ZWN0ZWQ6CiAgICAgICAgYm9vbCBibG9ja2luZ19tb2RlOwoKcHVibGljOgogICAg
ICAgIFdyaXRlYWJsZSh2b2lkKSA6IGJsb2NraW5nX21vZGUodHJ1ZSkgeyB9OwogICAgICAgIHZp
cnR1YWwgfldyaXRlYWJsZSh2b2lkKSB7IH07CgogICAgICAgIHZpcnR1YWwgdW5zaWduZWQgbG9u
ZyBld3JpdGUoY29uc3Qgdm9pZCAqIGJ1ZiwgdW5zaWduZWQgbG9uZyBsZW4pID0gMDsKCn07Cgpj
bGFzcyBSV2FibGUgOiBwdWJsaWMgUmVhZGFibGUsIHB1YmxpYyBXcml0ZWFibGUgewpwdWJsaWM6
CgogICAgICAgIFJXYWJsZSh2b2lkKSA6IFJlYWRhYmxlKCksIFdyaXRlYWJsZSgpIHsgfTsKICAg
ICAgICB2aXJ0dWFsIH5SV2FibGUodm9pZCkgeyB9OwoKfTsKCmNsYXNzIFBpcGUgOiBwdWJsaWMg
UldhYmxlIHsKCnB1YmxpYzoKICAgICAgICBQaXBlKHZvaWQpOwogICAgICAgIH5QaXBlKHZvaWQp
OwoKICAgICAgICB1bnNpZ25lZCBsb25nIGV3cml0ZShjb25zdCB2b2lkICogYnVmLCB1bnNpZ25l
ZCBsb25nIGxlbik7CgogICAgICAgIGludCBzZXRfd3JpdGVfYmxvY2tpbmcodm9pZCk7Cn07Cgp1
bnNpZ25lZCBsb25nIFBpcGU6OmV3cml0ZShjb25zdCB2b2lkICogYnVmLCB1bnNpZ25lZCBsb25n
IGxlbikgewoKICAgICAgICBpZiggIVdyaXRlYWJsZTo6YmxvY2tpbmdfbW9kZSApIHsKICAgICAg
ICAgICAgICAgIGlmIChzZXRfd3JpdGVfYmxvY2tpbmcoKSkgewogICAgICAgICAgICAgICAgICAg
ICAgICByZXR1cm4gMDsKICAgICAgICAgICAgICAgIH0KICAgICAgICB9Cgp9CgppbnQgUGlwZTo6
c2V0X3dyaXRlX2Jsb2NraW5nKHZvaWQpIHsKCiAgICAgICAgaWYgKFdyaXRlYWJsZTo6YmxvY2tp
bmdfbW9kZSkgcmV0dXJuIDA7Cgp9Cg==


             reply	other threads:[~2001-07-03  6:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03  6:56 niemayer [this message]
2001-07-07  7:21 lerdsuwa
2001-07-24  3:18 nathan
2001-07-25  2:39 nathan

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=20010703134731.31308.qmail@sourceware.cygnus.com \
    --to=niemayer@isg.de \
    --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).