public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gschmid@chello.fr
To: gcc-gnats@gcc.gnu.org
Subject: c++/9917: LANG problem gives an internal compiler error on some invalid code.
Date: Mon, 03 Mar 2003 12:56:00 -0000	[thread overview]
Message-ID: <20030303125215.29228.qmail@sources.redhat.com> (raw)

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


>Number:         9917
>Category:       c++
>Synopsis:       LANG problem gives an internal compiler error on some invalid code.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-illegal-code
>Submitter-Id:   net
>Arrival-Date:   Mon Mar 03 12:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Guillaume Schmid
>Release:        gcc 3.2.2
>Organization:
>Environment:
Updated Gentoo Linux.
LANG=fr_FR
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/specs
Configured with: /var/tmp/portage/gcc-3.2.2/work/gcc-3.2.2/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/3.2 --includedir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/3.2 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/3.2/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/3.2/info --enable-shared --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu --with-system-zlib --enable-languages=c,c++,ada,f77,objc,java --enable-threads=posix --enable-long-long --disable-checking --enable-cstdio=stdio --enable-clocale=generic --enable-__cxa_atexit --enable-version-specific-runtime-libs --with-gxx-include-dir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/include/g++-v3 --with-local-prefix=/usr/local --enable-shared --enable-nls --without-included-gettext
Thread model: posix
gcc version 3.2.2

>Description:
A simple error in my code triggered an internal compiler error ONLY if my environement variable LANG is fr_FR
the error output is correct if LANG=C.

here is the code:
------------------------- pipo.cc
struct pipo{
   int x;
};

int main (int argc, char **argv) {
   pipo p;
   p = 1;    // OK, real stupid :)
}
---------------------------- end
>How-To-Repeat:
Try to compile the given example code with LANG=FR_fr, I get the following:
---------------------------------
guillaume@ryuken pipo $ gcc pipo.cc
pipo.cc: Dans function « int main(int, char**) »:
pipo.cc:9: no match pour l'opérateur «
erreur interne de compilateur: erreur pour rapporter une routine ré-entée
SVP soumettre un rapport complet d'anomalies,
avec le source pré-traité si cela est approprié.
Consulter <URL:http://www.gnu.org/software/gcc/bugs.html> pour les instructions.
---------------------------------
It start with the beginning of an error message then there is an internal compiler error.

If I do the same thing with LANG=C, I get this:
guillaume@ryuken pipo $ g++ pipo.cc
pipo.cc: In function `int main(int, char**)':
pipo.cc:9: no match for `pipo& = int' operator
pipo.cc:1: candidates are: pipo& pipo::operator=(const pipo&)
----------------------------------------




>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-03-03 12:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 12:56 gschmid [this message]
2003-03-03 14:38 bangerth

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=20030303125215.29228.qmail@sources.redhat.com \
    --to=gschmid@chello.fr \
    --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).