Re: java/1840

Re: java/1840

[Tom Tromey]

The following reply was made to PR java/1840; it has been noted by GNATS.

From: Tom Tromey <tromey@redhat.com>
To: Marc Schmitt <schmitt@inf.ethz.ch>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/1840
Date: 06 Feb 2001 14:24:33 -0700

 >>>>> "Marc" == Marc Schmitt <schmitt@inf.ethz.ch> writes:
 
 Marc> I didn`t expect the workaround to be that simple, given the fact
 Marc> that gcc from the same snapshot accepts source files w/o
 Marc> specifying the encoding.
 
 Currently only the Java front end to gcc knows how to read files with
 arbitrary encodings.  The other front ends (at least C and C++) don't
 have any special handling here.
 
 I agree it is a bit confusing though.  I predict lots of reports like
 yours :-(
 
 Tom
>From neil@gcc.gnu.org Sun Apr 01 00:00:00 2001
From: neil@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c/1527
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <20010304110601.2800.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q1/msg01996.html
Content-length: 705

The following reply was made to PR c/1527; it has been noted by GNATS.

From: neil@gcc.gnu.org
To: ac9410@bellsouth.net, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: c/1527
Date: 4 Mar 2001 10:58:02 -0000

 Synopsis: initialization in zero-length array inside a nested structure
 
 State-Changed-From-To: open->closed
 State-Changed-By: neil
 State-Changed-When: Sun Mar  4 02:58:02 2001
 State-Changed-Why:
     This is a worthless bug report - you must provide preprocessed
     source.  Also, please do NOT use priorities of HIGH -
     they are reserved for GCC maintainers.
     
     I think the bug is fixed.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1527&database=gcc

Re: java/1840

[tromey]

The following reply was made to PR java/1840; it has been noted by GNATS.

From: tromey@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org, schmitt@inf.ethz.ch, tromey@gcc.gnu.org
Cc:  
Subject: Re: java/1840
Date: 6 Feb 2001 21:19:58 -0000

 Synopsis: unknown encoding: `ISO8859-1'
 
 State-Changed-From-To: feedback->closed
 State-Changed-By: tromey
 State-Changed-When: Tue Feb  6 13:19:58 2001
 State-Changed-Why:
     Workaround reported to work.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1840&database=gcc
>From rodrigc@gcc.gnu.org Sun Apr 01 00:00:00 2001
From: rodrigc@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/1808
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <20010311162601.28765.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q1/msg02187.html
Content-length: 520

The following reply was made to PR c++/1808; it has been noted by GNATS.

From: rodrigc@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org, kanitkar@akamai.com, nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/1808
Date: 11 Mar 2001 16:20:19 -0000

 Synopsis: Internal compiler error 390.
 
 State-Changed-From-To: open->closed
 State-Changed-By: rodrigc
 State-Changed-When: Sun Mar 11 08:20:19 2001
 State-Changed-Why:
     Does not result in ICE in GCC 3.0 branch
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1808&database=gcc

Re: java/1840

[tromey]

The following reply was made to PR java/1840; it has been noted by GNATS.

From: tromey@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, schmitt@inf.ethz.ch,
  tromey@gcc.gnu.org
Cc:  
Subject: Re: java/1840
Date: 3 Feb 2001 23:27:01 -0000

 Synopsis: unknown encoding: `ISO8859-1'
 
 Responsible-Changed-From-To: unassigned->tromey
 Responsible-Changed-By: tromey
 Responsible-Changed-When: Sat Feb  3 15:27:01 2001
 Responsible-Changed-Why:
     I'm looking at it.
 State-Changed-From-To: open->feedback
 State-Changed-By: tromey
 State-Changed-When: Sat Feb  3 15:27:01 2001
 State-Changed-Why:
     This bug occurs because the charset mentioned in
     your locale is not supported by the Solaris implementation
     of iconv().
     One workaround for you would be to always specify the
     encoding.  gcj is written to always accept the `UTF-8'
     encoding.  You can do this by running `gcj --encoding=UTF-8'
     
     Please tell me if that works for you.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1840&database=gcc
>From pme@gcc.gnu.org Sun Apr 01 00:00:00 2001
From: pme@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/2052
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <20010223183601.14495.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q1/msg01628.html
Content-length: 573

The following reply was made to PR c++/2052; it has been noted by GNATS.

From: pme@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, rbo@localhost.localdomain
Cc:  
Subject: Re: c++/2052
Date: 23 Feb 2001 18:30:13 -0000

 Synopsis: gcc 3.0 fails to recognize cout << flush;
 
 State-Changed-From-To: open->closed
 State-Changed-By: pme
 State-Changed-When: Fri Feb 23 10:30:13 2001
 State-Changed-Why:
     Fixed.  (Actually a libstdc++ problem, not c++.)  This will
     work for GCC 3.0.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2052&database=gcc