public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: paolo@gcc.gnu.org To: ebotcazou@libertysurf.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ghazi@caip.rutgers.edu, mark@codesourcery.com, nobody@gcc.gnu.org, paolo@gcc.gnu.org Subject: Re: libstdc++/10809: [3.3 regression] mips-sgi-irix6.5 libstdc++-v3 testsuite execution failure in 27_io/istream_unformatted.cc Date: Fri, 16 May 2003 17:25:00 -0000 [thread overview] Message-ID: <20030516172558.23772.qmail@sources.redhat.com> (raw) Synopsis: [3.3 regression] mips-sgi-irix6.5 libstdc++-v3 testsuite execution failure in 27_io/istream_unformatted.cc Responsible-Changed-From-To: unassigned->paolo Responsible-Changed-By: paolo Responsible-Changed-When: Fri May 16 17:25:57 2003 Responsible-Changed-Why: Analyzing. State-Changed-From-To: open->feedback State-Changed-By: paolo State-Changed-When: Fri May 16 17:25:57 2003 State-Changed-Why: Hi guys. I'm suspecting this commit (of mine ;): 2003-05-01 Paolo Carlini <pcarlini@unitus.it> Nathan Myers <ncm@cantrip.org> Backport from mainline fix of 2003-03-28. PR libstdc++/9533 I would appreciate if you could report on inadequacies for your favorite platforms of the various system call used in __basic_file<char>::showmanyc_helper (in config/io/basic_file_stdio.cc). In particular: does the autoconf test for 'fstat' succeed? If not, why? Thanks for your collaboration, Paolo. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10809
next reply other threads:[~2003-05-16 17:25 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-16 17:25 paolo [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-19 8:36 Eric Botcazou 2003-05-17 22:46 Paolo Carlini 2003-05-17 14:06 Eric Botcazou 2003-05-16 7:36 Eric Botcazou 2003-05-16 1:46 ghazi
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=20030516172558.23772.qmail@sources.redhat.com \ --to=paolo@gcc.gnu.org \ --cc=ebotcazou@libertysurf.fr \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=ghazi@caip.rutgers.edu \ --cc=mark@codesourcery.com \ --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).