This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH 05/11] Make expand_location resolve to locus in main source file

From: Jason Merrill <jason at redhat dot com>
To: Dodji Seketeli <dodji at redhat dot com>
Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Tom Tromey <tromey at redhat dot com>, Gabriel Dos Reis <gdr at integrable-solutions dot net>
Date: Wed, 11 Apr 2012 09:49:06 -0400
Subject: Re: [PATCH 05/11] Make expand_location resolve to locus in main source file
References: <m3hawr8wpz.fsf@redhat.com> <m3zkaj5puy.fsf@redhat.com>

On 04/10/2012 03:49 PM, Dodji Seketeli wrote:

Apparently, quite some places in the compiler (like the C/C++
preprocessor, the debug info machinery) expect expand_location to
resolve to locations that are in the main source file, even if the
token at stake comes from a macro that was defined in a header
somewhere.  Turning on -ftrack-macro-expansion by default was
triggering a lot of failures (not necessarily related to diagnostics)
because expand_location resolves to spelling locations instead.

Can you elaborate on these failures? For debug info I would think that the spelling location would be useful information, though I suppose without any way to "unwind" to the expansion context it could be a bit confusing. What is the problem for the preprocessor?

Jason

Follow-Ups:
- Re: [PATCH 05/11] Make expand_location resolve to locus in main source file
  - From: Dodji Seketeli

References:
- Patches to enable -ftrack-macro-expansion by default
  - From: Dodji Seketeli
- [PATCH 05/11] Make expand_location resolve to locus in main source file
  - From: Dodji Seketeli

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]