-
Notifications
You must be signed in to change notification settings - Fork 57
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
Enzyme compilation failed when using logpdf
#910
Comments
This looks to be lapack in particular, declare void @dpotrf_64_(i8*, i8*, i64, i8*, i64, i32) local_unnamed_addr #55 |
Is this an issue on my end or in general? Is there anything I could run to better assist in this issue? Thanks! |
This is an issue in general that we don't currently handle lapack functions. We (mostly @ZuseZ4 ) actually are presently working on adding BLAS & LaPack support at the moment. Alternatively, you could write a custom rule for whatever function calls the lapack function. @sethaxen may be able to help with this (see https://enzyme.mit.edu/julia/stable/generated/custom_rule/ for docs on custom rules). Finally, it may be useful to get a partial backtrace from the location that calls the lapack function, rather than just error if its called anywhere. To do so, you can add the function name (in this case dpotrf_64_ ) to this tuple: Line 6941 in c807462
|
This is the rule to port to Enzyme: There are some example implementations of BLAS rules here: #739 |
In any case since this is lapack support, am closing as a dup of #241 |
Example:
fails compilation
error is long and is given in error.txt
System info:
apologies if this is not enough information, please let me know if anything more is needed.
The text was updated successfully, but these errors were encountered: