GCC diagnostics and location-tracking improvements for GCC 8

Sep 10, 2017



I've got a number of proposals for improving diagnostics and how we track source locations in GCC, which I'd like to present at Cauldron; extending location-tracking to cover: (a) all expressions (including constants, and uses of a decl), not just compound expressions (b) other syntactic elements (e.g. for implementing IDE integration) I also want to discuss how we might help advanced users track how GCC is optimizing their code via some kind of hybrid of the dump_file and diagnostics subsystems. I plan for most of the session to be interactive, hence this feels like something of a "diagnostics and location-tracking BoF".



About GNU

The GNU Compiler Collection includes front ends for C, C++, Objective-C, Fortran, Ada, and Go, as well as libraries for these languages (libstdc++,...). GCC was originally written as the compiler for the GNU operating system. The GNU system was developed to be 100% free software, free in the sense that it respects the user's freedom.

Store presentation

Should this presentation be stored for 1000 years?

How do we store presentations

Total of 0 viewers voted for saving the presentation to eternal vault which is 0.0%


Recommended Videos

Presentations on similar topic, category or speaker