public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Deborah Schindall <dschindall@adirtech.com> To: bkoz@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: RE: libstdc++/6450: Using hex directive with insertion operator ( <<) does not Date: Fri, 31 May 2002 10:56:00 -0000 [thread overview] Message-ID: <20020531171604.12866.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/6450; it has been noted by GNATS. From: Deborah Schindall <dschindall@adirtech.com> To: "'bkoz@gcc.gnu.org'" <bkoz@gcc.gnu.org>, "'bkoz@gcc.gnu.org'" <bkoz@gcc.gnu.org>, "'dschindall@adirtech.com'" <dschindall@adirtech.com>, "'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>, "'gcc-prs@gcc.gnu.org'" <gcc-prs@gcc.gnu.org>, "'nobody@gcc.gnu.org'" <nobody@gcc.gnu.org>, "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org> Cc: Subject: RE: libstdc++/6450: Using hex directive with insertion operator ( <<) does not Date: Fri, 31 May 2002 13:16:02 -0400 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_01C208C6.D763BD60 Content-Type: text/plain This code works in GCC 3.1, I have reinstalled GCC 3.0.4 and have been unable to reproduce the bug. Thanks for the response. Gnat 6450 may be closed. Deborah > -----Original Message----- > From: bkoz@gcc.gnu.org [mailto:bkoz@gcc.gnu.org] > Sent: Wednesday, May 29, 2002 5:29 AM > To: bkoz@gcc.gnu.org; dschindall@adirtech.com; gcc-bugs@gcc.gnu.org; > gcc-prs@gcc.gnu.org; nobody@gcc.gnu.org > Subject: Re: libstdc++/6450: Using hex directive with > insertion operator > (<<) does not > > > Synopsis: Using hex directive with insertion operator (<<) does not > > Responsible-Changed-From-To: unassigned->bkoz > Responsible-Changed-By: bkoz > Responsible-Changed-When: Wed May 29 02:29:14 2002 > Responsible-Changed-Why: > Mine. > State-Changed-From-To: analyzed->feedback > State-Changed-By: bkoz > State-Changed-When: Wed May 29 02:29:14 2002 > State-Changed-Why: > I cannot reproduce this with gcc >= 3.1 on x86/linux. Can > you try this code with gcc-3.1 and see if it is still an > issue? If there's no response within a week, this bug report > will be closed. > > Thanks, > benjamin > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail& database=gcc&pr=6450 ------_=_NextPart_001_01C208C6.D763BD60 Content-Type: text/html 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=3DUS-ASCII"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2654.45"> <TITLE>RE: libstdc++/6450: Using hex directive with insertion operator = (<<) does not</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2>This code works in GCC 3.1, I have reinstalled GCC = 3.0.4 and have been unable to reproduce the bug. Thanks for the = response. Gnat 6450 may be closed.</FONT></P> <P><FONT SIZE=3D2>Deborah</FONT> </P> <P><FONT SIZE=3D2>> -----Original Message-----</FONT> <BR><FONT SIZE=3D2>> From: bkoz@gcc.gnu.org [<A = HREF=3D"mailto:bkoz@gcc.gnu.org">mailto:bkoz@gcc.gnu.org</A>]</FONT> <BR><FONT SIZE=3D2>> Sent: Wednesday, May 29, 2002 5:29 AM</FONT> <BR><FONT SIZE=3D2>> To: bkoz@gcc.gnu.org; dschindall@adirtech.com; = gcc-bugs@gcc.gnu.org;</FONT> <BR><FONT SIZE=3D2>> gcc-prs@gcc.gnu.org; nobody@gcc.gnu.org</FONT> <BR><FONT SIZE=3D2>> Subject: Re: libstdc++/6450: Using hex = directive with </FONT> <BR><FONT SIZE=3D2>> insertion operator</FONT> <BR><FONT SIZE=3D2>> (<<) does not</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> Synopsis: Using hex directive with insertion = operator (<<) does not</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> Responsible-Changed-From-To: = unassigned->bkoz</FONT> <BR><FONT SIZE=3D2>> Responsible-Changed-By: bkoz</FONT> <BR><FONT SIZE=3D2>> Responsible-Changed-When: Wed May 29 02:29:14 = 2002</FONT> <BR><FONT SIZE=3D2>> Responsible-Changed-Why:</FONT> <BR><FONT SIZE=3D2>> Mine.</FONT> <BR><FONT SIZE=3D2>> State-Changed-From-To: = analyzed->feedback</FONT> <BR><FONT SIZE=3D2>> State-Changed-By: bkoz</FONT> <BR><FONT SIZE=3D2>> State-Changed-When: Wed May 29 02:29:14 = 2002</FONT> <BR><FONT SIZE=3D2>> State-Changed-Why:</FONT> <BR><FONT SIZE=3D2>> I cannot reproduce this = with gcc >=3D 3.1 on x86/linux. Can </FONT> <BR><FONT SIZE=3D2>> you try this code with gcc-3.1 and see if it is = still an </FONT> <BR><FONT SIZE=3D2>> issue? If there's no response within a week, = this bug report </FONT> <BR><FONT SIZE=3D2>> will be closed.</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> Thanks,</FONT> <BR><FONT SIZE=3D2>> benjamin</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> <A = HREF=3D"http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&= " = TARGET=3D"_blank">http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20au= dit-trail&</A></FONT> <BR><FONT SIZE=3D2>database=3Dgcc&pr=3D6450</FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C208C6.D763BD60--
next reply other threads:[~2002-05-31 17:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-31 10:56 Deborah Schindall [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-03 2:39 libstdc++/6450: Using hex directive with insertion operator (<<) " bkoz 2002-05-29 2:44 bkoz 2002-05-24 11:36 paolo
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=20020531171604.12866.qmail@sources.redhat.com \ --to=dschindall@adirtech.com \ --cc=bkoz@gcc.gnu.org \ --cc=gcc-prs@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: linkBe 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).