This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug preprocessor/69093] New: implement -fmacro-backtrace-limit
- From: "patrick.pelissier at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 30 Dec 2015 18:05:39 +0000
- Subject: [Bug preprocessor/69093] New: implement -fmacro-backtrace-limit
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69093
Bug ID: 69093
Summary: implement -fmacro-backtrace-limit
Product: gcc
Version: 5.3.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: preprocessor
Assignee: unassigned at gcc dot gnu.org
Reporter: patrick.pelissier at gmail dot com
Target Milestone: ---
Recent gcc performs full backtrace when error / warning appear within a macro
but has not any option to limit its size.
This makes gcc hard to use for debugging deferred recursive macros (See
https://github.com/pfultz2/Cloak/wiki/C-Preprocessor-tricks,-tips,-and-idioms):
in such cases, the backtrace is huge (more than 5000 lines of backtrace per
instance) and useless.
clang has the option -fmacro-backtrace-limit for this purpose.