From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2105 invoked by alias); 23 Mar 2010 15:19:35 -0000 Received: (qmail 2012 invoked by uid 48); 23 Mar 2010 15:19:19 -0000 Date: Tue, 23 Mar 2010 15:19:00 -0000 Message-ID: <20100323151919.2011.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug preprocessor/7263] __extension__ keyword doesn't suppress warning on LL or ULL constants In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "tromey at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-03/txt/msg02322.txt.bz2 ------- Comment #21 from tromey at gcc dot gnu dot org 2010-03-23 15:19 ------- > What is missing from this patch? Is it only the macro location tracked or the parameter expanded within the macro? The biggest problem with the patch is that I didn't finish debugging it. It causes regressions of various kinds -- it is pretty buggy. There are a few FIXME comments marking known bad spots. It tracks the "full" location of each token. So, if a given token resulted from a macro expansion, you can determine the token's location from before the macro expansion (which might come from another macro expansion, or a macro definition, or be an argument to a macro invocation). It doesn't currently handle the original location of tokens arising from stringizing or pasting. > Does this enable us to track macro expansions like Clang? Yes. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7263