From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21729 invoked by alias); 9 Mar 2006 19:28:10 -0000 Received: (qmail 21621 invoked by alias); 9 Mar 2006 19:28:04 -0000 Date: Thu, 09 Mar 2006 19:28:00 -0000 Message-ID: <20060309192804.21620.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/26084] ICE (segfault) on C++ OpenMP code In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dnovillo at redhat dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-03/txt/msg00991.txt.bz2 List-Id: ------- 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