-
Notifications
You must be signed in to change notification settings - Fork 37
fix: finite diff gradient accidental type promotion + generalize inputs #1847
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
base: main
Are you sure you want to change the base?
Conversation
9afcb9a to
74f08fe
Compare
| resargprefix = gensym("finitediffresarg") | ||
|
|
||
| # TODO: can we detect and prevent using functions that mutate their arguments? | ||
| mlir_fn_res = TracedUtils.make_mlir_fn( |
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.
do we need to do the full make_mlir_fn here, or can we reuse the equivalent of traced call or traced functions to achieve the same effect?
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.
I am using make_mlir_fn mostly to linearlize the arguments. not sure how to use traced_call here though
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.
ah so it was linearization, not efficiency
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
precision issue will take a look later