This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH 12/13] Adjust relevant test cases wrt -ftrack-macro-expansion=[0|2]
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- 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>, Jason Merrill <jason at redhat dot com>, Paolo Carlini <paolo dot carlini at oracle dot com>, Benjamin De Kosnik <bkoz at redhat dot com>
- Date: Wed, 25 Apr 2012 10:25:17 -0500
- Subject: Re: [PATCH 12/13] Adjust relevant test cases wrt -ftrack-macro-expansion=[0|2]
- References: <firstname.lastname@example.org> <email@example.com>
On Wed, Apr 25, 2012 at 9:16 AM, Dodji Seketeli <firstname.lastname@example.org> wrote:
> Even after all the patches I have already submitted for this
> -ftrack-macro-expansion business, some test cases where errors happens
> on tokens that are defined in macros see their output change in an
> incompatible way, when you run them with or without
> I think this is expected, because the (spelling) locus inside the
> definition of the macro pointed to with -ftrack-macro-expansion is
> different from the locus of the expansion point of the macro pointed
> to without -ftrack-macro-expansion.
> In those cases this patch either adjusts the test case and forces it
> be run either with -ftrack-macro-expansion, or it just forces it to be
> run without -ftrack-macro-expansion.
> There are so many libstdc++ tests that were failing because of that
> benign issue that I preferred to just run them with
> -ftrack-macro-expansion diabled, after inspecting each of them to be
> sure there was nothing more serious underneath. ?I believe we can latter
> turn on -ftrack-macro-expansion there on a case by case basis.
> Boostrapped on x86_64-unknown-linux-gnu against trunk with and without
> -ftrack-macro-expansion turned on.