public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dnovillo at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/26084] ICE (segfault) on C++ OpenMP code
Date: Thu, 09 Mar 2006 19:28:00 -0000 [thread overview]
Message-ID: <20060309192804.21620.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26084-2736@http.gcc.gnu.org/bugzilla/>
------- Comment #12 from dnovillo at redhat dot com 2006-03-09 19:28 -------
Subject: Re: ICE (segfault) on C++ OpenMP code
On 03/09/06 14:17, pinskia at gcc dot gnu dot org wrote:
> If you had written a status on this bug before I closed it as a dup,
> I would not have closed it as a dup because I would have read that it
> was not fully a dup.
>
When in doubt, ask. I don't have the time you seem to have to keep a
perfectly up-to-date status on the PRs I have in my queue.
I understand that you as a bugmaster would like to minimize open PRs and
have perfect information on all of them, but such is life. It's an
imperfect system and the bugs will not always have all the information
you want in them.
Unless you are absolutely certain (i.e., you have worked on a patch or
debugged the problem in detail), you should ask the developer who was
last working on the bug to see what the status is.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26084
next prev parent reply other threads:[~2006-03-09 19:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 23:46 [Bug c++/26084] New: [gomp-branch] ICE (segfault) on C++ OpenMP coce martin at mpa-garching dot mpg dot de
2006-02-02 23:48 ` [Bug c++/26084] " martin at mpa-garching dot mpg dot de
2006-02-04 11:32 ` martin at mpa-garching dot mpg dot de
2006-02-06 9:40 ` [Bug c++/26084] [gomp-branch] ICE (segfault) on C++ OpenMP code reichelt at gcc dot gnu dot org
2006-02-06 11:15 ` martin at mpa-garching dot mpg dot de
2006-02-07 10:44 ` martin at mpa-garching dot mpg dot de
2006-02-07 12:12 ` dnovillo at gcc dot gnu dot org
2006-03-09 18:49 ` [Bug c++/26084] " pinskia at gcc dot gnu dot org
2006-03-09 19:01 ` dnovillo at gcc dot gnu dot org
2006-03-09 19:04 ` pinskia at gcc dot gnu dot org
2006-03-09 19:10 ` dnovillo at redhat dot com
2006-03-09 19:17 ` pinskia at gcc dot gnu dot org
2006-03-09 19:28 ` dnovillo at redhat dot com [this message]
2006-03-22 12:33 ` rth at gcc dot gnu dot org
2006-03-22 12:50 ` [Bug middle-end/26084] " rth at gcc dot gnu dot org
2006-03-22 12:53 ` rth at gcc dot gnu dot org
2006-03-22 14:37 ` martin at mpa-garching dot mpg dot de
2006-03-23 11:37 ` reichelt at gcc dot gnu dot org
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=20060309192804.21620.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--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: 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).