public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: sdementen@hotmail.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/8160: Internal compiler error in build_modify_expr, at cp/typeck.c:5494
Date: Mon, 07 Oct 2002 08:16:00 -0000	[thread overview]
Message-ID: <20021007151347.19991.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]


>Number:         8160
>Category:       c++
>Synopsis:       Internal compiler error in build_modify_expr, at cp/typeck.c:5494
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-illegal-code
>Submitter-Id:   net
>Arrival-Date:   Mon Oct 07 08:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Sébastien de Menten
>Release:        gcc version 3.2 (Mandrake Linux 9.0 3.2-1mdk)
>Organization:
>Environment:
Fresh Mandrake 9.0 installation (gcc-2.96 is also installed)
>Description:
Compilation of the file leads to

error_build_modify_expr.cpp: In constructor `foo<D>::foo() [with int D = 1]':
error_build_modify_expr.cpp:15:   instantiated from here
error_build_modify_expr.cpp:11: Internal compiler error in build_modify_expr, at cp/typeck.c:5494
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:https://qa.mandrakesoft.com/> for instructions.
>How-To-Repeat:
Compile the file with no special flags

g++ error_build_modify_expr.cpp
>Fix:
Remove the templateness of the file (in this case, the template is useless :-)).
Otherwise, this is not possible. The const array must be initialised in another way.
But the standard C++ does not define any way, I think...
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-c++src; name="error_build_modify_expr.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="error_build_modify_expr.cpp"

I2luY2x1ZGUgPGlvc3RyZWFtPgoKdGVtcGxhdGU8aW50IEQ+CmNsYXNzIGZvbyB7CnB1YmxpYzoK
ICBjb25zdCBpbnQgZFszXTsKICBmb28oKTsKfTsKCnRlbXBsYXRlPGludCBEPgpmb288RD46OmZv
bygpIDogZCgoY29uc3QgaW50W10pezEsMiwzfSkgewp9OwoKaW50IG1haW4oaW50IGFyZ2MsY2hh
ciAqKmFyZ3YpIHsKICBmb288MT4gYjsKfTsK


             reply	other threads:[~2002-10-07 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-07  8:16 sdementen [this message]
2002-10-27  6:44 lerdsuwa

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=20021007151347.19991.qmail@sources.redhat.com \
    --to=sdementen@hotmail.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).