- Notifications
You must be signed in to change notification settings - Fork 15.3k
Open
Labels
bugzillaIssues migrated from bugzillaIssues migrated from bugzillaclang:diagnosticsNew/improved warning or error message in Clang, but not in clang-tidy or static analyzerNew/improved warning or error message in Clang, but not in clang-tidy or static analyzer
Description
| Bugzilla Link | 3814 |
| Version | unspecified |
| OS | Linux |
| Reporter | LLVM Bugzilla Contributor |
| CC | @lattner,@tkremenek,@pwo,@rjmccall |
Extended Description
clang is very noisy by default on projects using gettext, because the format string literal warning is on by default, and it warns about code like
printf(_("some string"), ...);
where _ is a macro for some gettext function.
How crude would it be to recognize this pattern explicitly? I.e. printf of a direct call of a function taking a single literal string and returning a const char*.
Metadata
Metadata
Assignees
Labels
bugzillaIssues migrated from bugzillaIssues migrated from bugzillaclang:diagnosticsNew/improved warning or error message in Clang, but not in clang-tidy or static analyzerNew/improved warning or error message in Clang, but not in clang-tidy or static analyzer