You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
clang-format now formats the following code differently:
This:
static cl::opt
ValueDependences("polly-value-dependences",
cl::desc("Use value instead of memory based dependences"),
cl::Hidden, cl::init(true), cl::cat(PollyCategory));
became:
static cl::opt
ValueDependences("polly-value-dependences",
cl::desc("Use value instead of memory based dependences"),
cl::Hidden, cl::init(true), cl::cat(PollyCategory));
I can see the reasoning behind this, but a quick grep 'grep -R cl::opt -A 2 lib/'
does not show a single use of this in LLVM whereas the first one is very common.
I believe this change should be disabled in the LLVM style
The text was updated successfully, but these errors were encountered:
Extended Description
Hi,
clang-format now formats the following code differently:
This:
static cl::opt
ValueDependences("polly-value-dependences",
cl::desc("Use value instead of memory based dependences"),
cl::Hidden, cl::init(true), cl::cat(PollyCategory));
became:
static cl::opt
ValueDependences("polly-value-dependences",
cl::desc("Use value instead of memory based dependences"),
cl::Hidden, cl::init(true), cl::cat(PollyCategory));
I can see the reasoning behind this, but a quick grep 'grep -R cl::opt -A 2 lib/'
does not show a single use of this in LLVM whereas the first one is very common.
I believe this change should be disabled in the LLVM style
The text was updated successfully, but these errors were encountered: