On Wed, Apr 25, 2012 at 9:16 AM, Dodji Seketeli <do...@redhat.com> 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 > -ftrack-macro-expansion. > > 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.
OK. -- Gaby
