From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5735 invoked by alias); 19 Jun 2014 20:46:22 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 5725 invoked by uid 89); 19 Jun 2014 20:46:21 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 19 Jun 2014 20:46:20 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s5JKkHL0001998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 19 Jun 2014 16:46:18 -0400 Received: from barimba (ovpn-113-103.phx2.redhat.com [10.3.113.103]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s5JKkG5Z018790 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NO); Thu, 19 Jun 2014 16:46:16 -0400 From: Tom Tromey To: "Joseph S. Myers" Cc: Subject: Re: [PATCH 2/5] c_diagnostic_ignored_function hack References: <1400254001-12038-1-git-send-email-tromey@redhat.com> <1400254001-12038-3-git-send-email-tromey@redhat.com> Date: Thu, 19 Jun 2014 20:46:00 -0000 In-Reply-To: (Joseph S. Myers's message of "Fri, 16 May 2014 16:04:59 +0000") Message-ID: <87k38cbpbc.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2014-06/txt/msg01567.txt.bz2 Joseph> I'd say this global actually belongs somewhere in the Joseph> diagnostic_context (i.e., instead of the Joseph> diagnostic_context_auxiliary_data (DC) actually being a tree as Joseph> it is at present, it should point to a structure with whatever Joseph> extra information clients wish to use to control aspects of Joseph> diagnostic reporting). We dropped this patch from the series and instead the diagnostic stuff is all handled in the plugin itself. You can see it in the new patch #5. Tom