public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: brister@nominum.com To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/8231: iostream header position causes bad code generation Date: Sat, 02 Nov 2002 13:16:00 -0000 [thread overview] Message-ID: <20021102211600.30407.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/8231; it has been noted by GNATS. From: brister@nominum.com To: paolo@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: libstdc++/8231: iostream header position causes bad code generation Date: Sat, 2 Nov 2002 22:06:20 +0100 I'm sorry, but I don't have the original any more. It was under rapid change so I merged the files together and made it as simple as possible to show the bug. > Synopsis: iostream header position causes bad code generation > State-Changed-From-To: open->feedback > State-Changed-By: paolo > State-Changed-When: Sat Nov 2 12:48:37 2002 > State-Changed-Why: > I can reproduce the problem on i686-pc-linux-gnu from > your preprocessed file. > However, could you possibly provide also the plain source > and describe the problem referring to specific line > numbers of it? This would speed-up the processing of the PR. > Thanks, Paolo. > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8231 -- James Brister brister@nominum.com Nominum Inc.
next reply other threads:[~2002-11-02 21:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-02 13:16 brister [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-04 14:32 ljrittle 2002-11-02 13:43 paolo 2002-11-02 12:48 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=20021102211600.30407.qmail@sources.redhat.com \ --to=brister@nominum.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: 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).