From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27497 invoked by alias); 7 Dec 2015 10:31:42 -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 27475 invoked by uid 89); 7 Dec 2015 10:31:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_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; Mon, 07 Dec 2015 10:31:40 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (Postfix) with ESMTPS id 2F80DA0B4A for ; Mon, 7 Dec 2015 10:31:39 +0000 (UTC) Received: from localhost.localdomain (vpn1-6-50.ams2.redhat.com [10.36.6.50]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tB7AVbbr005217; Mon, 7 Dec 2015 05:31:38 -0500 Subject: Re: [PATCH] Fix missing range information for "%q+D" format code To: David Malcolm References: <1449174784-60819-1-git-send-email-dmalcolm@redhat.com> <56617460.8010208@redhat.com> <1449261952.8490.55.camel@surprise> <1449263389.8490.60.camel@surprise> Cc: gcc-patches@gcc.gnu.org From: Bernd Schmidt Message-ID: <56656009.7060603@redhat.com> Date: Mon, 07 Dec 2015 10:31:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <1449263389.8490.60.camel@surprise> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-12/txt/msg00707.txt.bz2 On 12/04/2015 10:09 PM, David Malcolm wrote: > Updated patch to comment attached, which rewrites things to clarify the > meaning of SHOW_CARET_P. I guess this is OK for now. I think I'll go play with the Fortran frontend a bit to see what exactly is going on with its use of set_range there, I still think that function is a little clunky. Bernd