public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: chikayama@logos.t.u-tokyo.ac.jp
To: gcc-gnats@gcc.gnu.org
Subject: c++/3704: Internal compiler error 390
Date: Mon, 16 Jul 2001 19:46:00 -0000	[thread overview]
Message-ID: <20010717023517.3110.qmail@sourceware.cygnus.com> (raw)

>Number:         3704
>Category:       c++
>Synopsis:       Internal compiler error 390
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 16 19:46:02 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Takashi Chikayama
>Release:        gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
>Organization:
>Environment:
Linux katsura 2.4.2 #9 Sat Jun 30 10:39:26 JST 2001 i686 unknown
libc-2.1.3
>Description:
G++ reports internal compiler error 390
on compiling the following.

#include <stl.h>

static int
new_track() {
  printf("%c", count);
}
>How-To-Repeat:
Compiling it again.
>Fix:
?
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-07-16 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-16 19:46 chikayama [this message]
2001-08-10  8:29 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=20010717023517.3110.qmail@sourceware.cygnus.com \
    --to=chikayama@logos.t.u-tokyo.ac.jp \
    --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).