[Bug c++/45333] Include macros in instantiation backtraces

2011-10-20 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45333 --- Comment #5 from Manuel López-Ibáñez 2011-10-20 09:11:42 UTC --- (In reply to comment #4) > > Agreed again. I suspect this is related to our (ab)use of the global > input_location instead of relying on the precise location of the tokens > we

[Bug c++/45333] Include macros in instantiation backtraces

2011-10-20 Thread dodji at seketeli dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45333 --- Comment #4 from dodji at seketeli dot org 2011-10-20 08:57:06 UTC --- > So we can track the origin of the instantation to the macro definition, but > then we don't show where the macro is invoked from, which is shown without > -ftrack-macro-e

[Bug c++/45333] Include macros in instantiation backtraces

2011-10-20 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45333 Manuel López-Ibáñez changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c++/45333] Include macros in instantiation backtraces

2011-10-20 Thread dodji at seketeli dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45333 --- Comment #2 from dodji at seketeli dot org 2011-10-20 08:25:20 UTC --- Yes, it's related. With the infrastructure that is in right now, the results are not super for template instantiate backtraces though: $ cat -n test.cc 1#define

[Bug c++/45333] Include macros in instantiation backtraces

2011-10-19 Thread paolo.carlini at oracle dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45333 Paolo Carlini changed: What|Removed |Added CC|gcc-bugs at gcc dot gnu.org |dodji at gcc dot gnu.org --- Comment #1 f