public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: benoit.sibaud@rd.francetelecom.com, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, gdr@gcc.gnu.org,
	gdr@integrable-solutions.net, nobody@gcc.gnu.org
Subject: Re: c++/8846: [3.2 regression] ICE: locales and no match for operator<</operator+
Date: Fri, 06 Dec 2002 08:56:00 -0000	[thread overview]
Message-ID: <20021206165637.30961.qmail@sources.redhat.com> (raw)

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

Old Synopsis: ICE: locales and no match for operator<</operator+
New Synopsis: [3.2 regression] ICE: locales and no match for operator<</operator+

Responsible-Changed-From-To: unassigned->gdr
Responsible-Changed-By: bangerth
Responsible-Changed-When: Fri Dec  6 08:56:36 2002
Responsible-Changed-Why:
    He fixed something similar recently
State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Fri Dec  6 08:56:36 2002
State-Changed-Why:
    Confirmed. With 3.2.2CVS of yesterday (12/5/02), I get
    
    tmp/g> LC_ALL=fr_FR@euro /home/bangerth/bin/gcc-3.2.2-pre/bin/c++ -c x.cc
    x.cc: Dans function « int main() »:
    x.cc:8: 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.
    
    (and yes, even I can see that this is horrible "franglais").
    
    With 3.3 and 2.95 I get an error, but no ICE.
    
    Gaby, did your patch make it to the branch?
    
    Regards
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8846


             reply	other threads:[~2002-12-06 16:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06  8:56 bangerth [this message]
2003-04-25 21:05 jbuck

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=20021206165637.30961.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=benoit.sibaud@rd.francetelecom.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=gdr@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --cc=nobody@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).