public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu> To: Dara Hazeghi <dhazeghi@yahoo.com> Cc: gcc-bugs@gcc.gnu.org Subject: Re: NEW vs. UNCONFIRMED Date: Mon, 02 Jun 2003 15:53:00 -0000 [thread overview] Message-ID: <Pine.LNX.4.44.0306021049340.21442-100000@gandalf.ices.utexas.edu> (raw) In-Reply-To: <6E8F0674-93E8-11D7-81B9-000393681B36@yahoo.com> > Yes, that makes more sense. I think the general policy should be that > bugs get closed only when there's good evidence that they've been > fixed, Certainly. Use common sense. > No, but what I mean is that C/C++ bugs are _generally_ reproducible > across targets, meaning you don't need a specific machine to test them Not quite. We've got a number of PRs for windows specific things. But in general true. > > Dara seems like everything else :-) > > Not quite. Right now I have access to PowerPC/Darwin, x86/Linux, > Sparc/Solaris. Hopefully this summer: HPPA/HPUX, IA64/HPUX, and > IA64/Linux. That _is_ almost everything else :-) > Looks like the main missing ones are MIPS/IRIX, Alpha/Tru64 and the > small embedded ones (SH, Arm, etc.). I've got an old mips/irix machine, but it took 3 days to bootstrap 3.2.3, and 3.3 didn't build at all... > P.S. Could somebody take a look at 10922 sometime? I definitely should > have taken a C++ course earlier this year, but until then... We're already pretty well staffed in the C++ area. You're doing great in others. So why generate overlap :-) Can you send me preprocessed sources for the 3.4 failure, and how that one line originally looked like? W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ices.utexas.edu www: http://www.ices.utexas.edu/~bangerth/
next prev parent reply other threads:[~2003-06-02 15:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-06-01 4:21 Dara Hazeghi 2003-06-02 15:53 ` Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-06-01 4:25 Dara Hazeghi [not found] <486DCCCA-93CC-11D7-A14F-000393681B36@yahoo.com> 2003-06-01 1:15 ` Wolfgang Bangerth 2003-06-01 1:32 ` Andrew Pinski 2003-06-01 1:38 ` Wolfgang Bangerth 2003-06-01 3:56 ` Tim Prince 2003-06-01 1:01 Dara Hazeghi 2003-06-02 7:32 ` Ben Elliston
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=Pine.LNX.4.44.0306021049340.21442-100000@gandalf.ices.utexas.edu \ --to=bangerth@ices.utexas.edu \ --cc=dhazeghi@yahoo.com \ --cc=gcc-bugs@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).