public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jianhua Zhou <Jianhua.Zhou@informix.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: c++/5197: compiler doesn't work correctly
Date: Wed, 09 Jan 2002 16:06:00 -0000 [thread overview]
Message-ID: <20020110000600.14712.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/5197; it has been noted by GNATS.
From: Jianhua Zhou <Jianhua.Zhou@informix.com>
To: "'rodrigc@gcc.gnu.org'" <rodrigc@gcc.gnu.org>,
"'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>, "'gcc-prs@gcc.gnu.org'"
<gcc-prs@gcc.gnu.org>, "'jianhua.zhou@mail2ext.na.informix.com'"
<jianhua.zhou@mail2ext.na.informix.com>, "'nobody@gcc.gnu.org'"
<nobody@gcc.gnu.org>, "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>,
Jianhua Zhou <Jianhua.Zhou@informix.com>
Cc:
Subject: RE: c++/5197: compiler doesn't work correctly
Date: Wed, 9 Jan 2002 17:52:16 -0600
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C19968.AACCC6C0
Content-Type: text/plain;
charset="ISO-8859-1"
Yes. It is ok on 3.0.3
But g++ 3.0.3 is more ANSI C++ standard. We are using a lot feature which
are not available in g++ 3.0.3.
So would you please check the g++ 2.9.6 (RedHat 7.1) and see if this problem
is there. Or give me some a
2.9.x version, which is restricted to ANSI C++, has this problem fixed.
Thanks!
-----Original Message-----
From: rodrigc@gcc.gnu.org [mailto:rodrigc@gcc.gnu.org]
Sent: Wednesday, December 26, 2001 5:13 PM
To: gcc-bugs@gcc.gnu.org; gcc-prs@gcc.gnu.org;
jianhua.zhou@informix.com; nobody@gcc.gnu.org
Subject: Re: c++/5197: compiler doesn't work
correctly
Synopsis: compiler doesn't work correctly
State-Changed-From-To: open->feedback
State-Changed-By: rodrigc
State-Changed-When: Wed Dec 26 16:12:44 2001
State-Changed-Why:
I cannot reproduce this problem with gcc 3.0.3 under
Linux.
Can you try gcc 3.0.3 and see if the problem is
reproduced?
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
r=5197
------_=_NextPart_001_01C19968.AACCC6C0
Content-Type: text/html;
charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: c++/5197: compiler doesn't work correctly</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2 FACE=3D"Arial">Yes. It is ok on 3.0.3</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">But g++ 3.0.3 is more ANSI C++ =
standard. We are using a lot feature which are not available in g++ =
3.0.3.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">So would you please check the g++ =
2.9.6 (RedHat 7.1) and see if this problem is there. Or give me some =
a</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">2.9.x version, which is restricted to =
ANSI C++, has this problem fixed.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks! </FONT>
</P>
<UL><UL>
<P><A NAME=3D"_MailData"><FONT SIZE=3D2 FACE=3D"Arial">-----Original =
Message-----</FONT></A>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">From: =
rodrigc@gcc.gnu.org [<A =
HREF=3D"mailto:rodrigc@gcc.gnu.org">mailto:rodrigc@gcc.gnu.org</A>]</FON=
T></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Sent: </FONT></B> <FONT =
SIZE=3D2 FACE=3D"Arial">Wednesday, December 26, 2001 5:13 PM</FONT>
<BR><B><FONT SIZE=3D2 =
FACE=3D"Arial">To: </FONT></B> <FONT SIZE=3D2 =
FACE=3D"Arial">gcc-bugs@gcc.gnu.org; gcc-prs@gcc.gnu.org; =
jianhua.zhou@informix.com; nobody@gcc.gnu.org</FONT>
<BR><B><FONT SIZE=3D2 =
FACE=3D"Arial">Subject: </FONT>=
</B> <FONT SIZE=3D2 FACE=3D"Arial">Re: c++/5197: compiler doesn't work =
correctly</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Synopsis: compiler doesn't work =
correctly</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">State-Changed-From-To: =
open->feedback</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">State-Changed-By: rodrigc</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">State-Changed-When: Wed Dec 26 =
16:12:44 2001</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">State-Changed-Why:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial"> I cannot reproduce =
this problem with gcc 3.0.3 under Linux.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial"> Can you try gcc =
3.0.3 and see if the problem is reproduced?</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&=
database=3Dgcc&pr=3D5197" =
TARGET=3D"_blank">http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20au=
dit-trail&database=3Dgcc&pr=3D5197</A></FONT>
</P>
</UL></UL>
</BODY>
</HTML>
------_=_NextPart_001_01C19968.AACCC6C0--
next reply other threads:[~2002-01-10 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 16:06 Jianhua Zhou [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-03 10:52 rodrigc
2002-01-09 16:16 Jianhua Zhou
2001-12-27 9:16 Jianhua Zhou
2001-12-26 16:12 rodrigc
2001-12-26 14:36 jianhua.zhou
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=20020110000600.14712.qmail@sources.redhat.com \
--to=jianhua.zhou@informix.com \
--cc=gcc-prs@gcc.gnu.org \
--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).