public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rmincold@dreamscape.com
To: gcc-gnats@gcc.gnu.org
Subject: ada/8129: Compiler seems unable to process function pointers to member functions.
Date: Wed, 02 Oct 2002 17:46:00 -0000	[thread overview]
Message-ID: <20021003003814.3093.qmail@sources.redhat.com> (raw)


>Number:         8129
>Category:       ada
>Synopsis:       Compiler seems unable to process function pointers to member functions.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 02 17:46:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Richard Miller
>Release:        GNU general version 2, 1991 Free Software foundation IDG Books Standard C++ Bible
>Organization:
>Environment:
Windows 98
>Description:
 Here is result of compile attempt:

c:\quincy99\output\sam's\list14-11.cpp: In function `int main()':
c:\quincy99\output\sam's\list14-11.cpp:32: Internal compiler error in `const_hash', at varasm.c:2372
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/faq.html#bugreport> for instructions.
>How-To-Repeat:
Try compiling.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="list14-11.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="list14-11.cpp"

Ly9MaXN0aW5nIDE0LjExIEFycmF5IG9mIHBvaW5lcnMgdG8gbWVtYmVyIGZ1bmN0aW9ucw0KDQoj
aW5jbHVkZSA8aW9zdHJlYW0+DQoNCmNsYXNzIERvZw0Kew0KcHVibGljOg0KCXZvaWQgU3BlYWso
KSBjb25zdCB7Y291dDw8Ildvb2YhXG4iO30NCgl2b2lkIE1vdmUoKSBjb25zdCB7Y291dDw8Ildh
bGtpbmcgdG8gaGVlbFxuIjt9DQoJdm9pZCBFYXQoKSBjb25zdCB7Y291dDw8IkdvYmJsaW5nIGZv
b2RcbiI7fQ0KCXZvaWQgR3Jvd2woKSBjb25zdCB7Y291dDw8IkdycnJyXG4iO30NCgl2b2lkIFdo
aW1wZXIoKSBjb25zdCB7Y291dDw8IldoaW5uaW5nIG5vaXNlc1xuIjt9DQoJdm9pZCBSb2xsT3Zl
cigpIGNvbnN0IHtjb3V0PDwiUm9sbGluZyBvdmVyXG4iO30NCgl2b2lkIFBsYXlEZWFkKCkgY29u
c3QgeyJJcyB0aGlzIHRoZSBlbmQgb2YgTGl0dGxlIENlYXNlcj9cbiI7fSANCn07Ly9lbmQgY2xh
c3MgRG9nDQoNCnR5cGVkZWYgdm9pZCAoRG9nOjoqUERGKSgpIGNvbnN0IDsNCg0KaW50IG1haW4o
KQ0Kew0KCWNvbnN0IGludCBtYXhGdW5jcyA9IDc7DQoJDQoJUERGIERvZ0Z1bmN0aW9uc1sgbWF4
RnVuY3MgXT0NCgl7DQoJCSZEb2c6OiBTcGVhayAsDQoJCSZEb2c6OiBNb3ZlICwNCgkJJkRvZzo6
IEVhdCAsDQoJCSZEb2c6OiBHcm93bCAsDQoJCSZEb2c6OldoaW1wZXIgLA0KCQkmRG9nOjogUm9s
bE92ZXIgLA0KCQkmRG9nOjogUGxheURlYWQgDQoJfTsvL2VuZCBQREYgRG9nRnVuY3Rpb25zWyBt
YXhGdW5jdGlvbnMgXT0NCi8qDQoJRG9nICogcERvZyA9IDA7DQoJaW50IG1ldGhvZCA7DQoJYm9v
bCBmUXVpdCA9IGZhbHNlIDsNCgl3aGlsZSghIGZRdWl0ICkNCgl7DQoJCWNvdXQ8PCIoMClRdWl0
ICgxKVNwZWFrICgyKU1vdmUgKDMpRWF0ICg0KUdyb3dsIjsNCgkJY291dDw8IiAoNSlXaGltcGVy
ICg2KVJvbGwgT3ZlciAoNykgUGxheSBEZWFkOiAiOw0KCQljaW4+PiBtZXRob2QgOw0KCQlpZigg
bWV0aG9kID09IDApDQoJCQlmUXVpdCA9IHRydWUgOw0KCQllbHNlDQoJCXsNCgkJCXBEb2cgPSBu
ZXcgRG9nIDsNCgkJCXBEb2cgLT4gKiBEb2dGdW5jdGlvbnNbIG1ldGhvZCAtIDFdKCk7DQoJCQlk
ZWxldGUgcERvZyA7DQoJCX0vL2Vsc2UgaWYoIG1ldG5vZCA9PSAwKQ0KCX0vL2VuZCB3aGlsZSgh
IGZRdWl0ICkNCiovCXJldHVybiAwOw0KfS8vZW5kIGludCBtYWluKCkNCg==


                 reply	other threads:[~2002-10-03  0:46 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=20021003003814.3093.qmail@sources.redhat.com \
    --to=rmincold@dreamscape.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).