-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ORE and better phi unwrapping #139
Conversation
@@ -116,19 +130,30 @@ Value *GradientUtils::unwrapM(Value *const val, IRBuilder<> &BuilderM, | |||
} | |||
} | |||
|
|||
// llvm::errs() << "uwval: " << *val << "\n"; | |||
#define getOp(v) \ | |||
#define getOpFullest(vtmp, frominst, check) \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it make sense to turn this into an inlined function instead of a macro?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function was apparently a major performance bottleneck, thus why it became a macro. For release builds it doesn't matter, but I presume marking as inline won't actually inline in debug builds?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right I forget that GCC/Clang ignores force inlining in debug mode.
No description provided.