- User Since
- Mar 2 2020, 4:41 AM (33 w, 5 d)
Thu, Oct 22
Sep 2 2020
Aug 21 2020
Aug 10 2020
Add a test that checks that clang accepts -Wa,--generate-missing-build-notes=yes and -Wa,--generate-missing-build-notes=no
Jul 29 2020
Jun 5 2020
I'm looking at this again and I am not sure how it is meant to work. For example in Parser::parseClassSpecifier in ParseDeclCXX.cpp.
Here attrs is a local variable of type ParsedAttributesWithRange, already before my patch. attrs is then passed to
Mar 31 2020
Sorry for taking so long but it seems like I've went down a rabbit hole a bit. My previous patch sets the range in parseGNUAttributes() unconditionally, but that seems to trigger cases such as
Mar 23 2020
Thanks, I'll take a look at the tests.
Mar 11 2020
Updated according to Aaron's comments. I'm not sure about changing the DeclSpec member and moving ParsedAttributesWithRange to ParsedAttr.h.
Mar 9 2020
Mar 4 2020
I know this has been reverted, but for the record, the implementation has a few shortcomings that makes it hard to use it for projects that rely on fallthrough comments:
Mar 3 2020
fallthrough comment detection has been reverted, so abandon this in the meantime.