- User Since
- Jun 10 2016, 1:55 AM (97 w, 1 d)
Wed, Apr 18
Mon, Apr 16
Wed, Apr 11
Hi! We have encountered a regression where clang-tidy leaves behind temporary files after this change. I wrote a PR for that: https://bugs.llvm.org/show_bug.cgi?id=37091.
Wed, Mar 28
Our legacy frontend does not support -MJ, so when using that frontend for code generation, we invoke clang with -MJ, and at the same use -fsyntax-only to get the improved diagnostics that clang provides. This is idiosyncratic and probably hacky, I know, but it works well enough to for example for getting access to defines and include flags from the compilation database, and being able to run clang-tidy. So (1) does not fit our use case, unfortunately.
With this change, we will emit the .file 0 directive even for -gdwarf-. The directive results in an error when assembling with GAS. Should this be seen as a problem, or is it something that we accept?
Mon, Mar 26
Downstream we use -MJ in a bit of an idiosyncratic way, as we're in a transition period where we, for a subset of the code base, only use the clang frontend for diagnostics, and not for the code generation. However, if you don't think that using -fsyntax-only and -MJ makes sense in any upstream application, I'll drop from this change. I'm leaving the assertion as-is.
Mar 22 2018
Mar 16 2018
A small caveat with this patch is that it does not fix the case where the input file as also added as an extra dependency with -fdepfile-entry; however, I reasoned that it shouldn't really be a problem in practice. I thought that it was a good trade-off ignoring that for slightly simpler code.
Mar 2 2018
Feb 1 2018
Removed nonessential attributes.
Jan 26 2018
Jan 25 2018
Jan 24 2018
Oct 18 2017
Unless I'm mistaken, int_experimental_gc_statepoint should also be marked recursive?
Sep 26 2017
Simplified the test case according to dblaikie's comment (thanks!).
Sep 25 2017
Sep 22 2017
Aug 23 2017
Changed so that the debug location is kept in the other cases.
Added CHECK statements (thanks for pointing that out!).