Skip to content

Conversation

@ngimel
Copy link
Collaborator

@ngimel ngimel commented Jul 19, 2020

On some systems/mkl versions it produces expm1(nan)=-1

@ngimel ngimel requested a review from smessmer July 19, 2020 17:26
Copy link
Contributor

@facebook-github-bot facebook-github-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ngimel has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@mruberry mruberry self-requested a review July 21, 2020 05:16
@facebook-github-bot
Copy link
Contributor

@ngimel merged this pull request in fe41558.

@mingfeima
Copy link
Collaborator

@ngimel Hi, could you please provide more info on what the system/mkl config is that goes wrong for torch.expm1().

The expected behavior is to return a NaN for a NaN input, right?

>>> torch.Tensor([float('nan')]).expm1()
tensor([nan])

@CaoZhongZ
Copy link
Contributor

@vpirogov

@vpirogov
Copy link

vpirogov commented Jul 31, 2020

According to Intel MKL documentation expm1 function should be indeed returning NaN in this scenario. In case there's a bug in implementation I would like to report this to Intel MKL development team. Could you please provide information on what systems and library versions the issue is observed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants