Wrong logarithm of BigInteger when size of BigInteger exceeds ¼ gigabyte - by JeppeSN1

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 776946 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/18/2013 2:19:44 PM
Access Restriction Public

Description

When the size of a (positive) BigInteger (from System.Numerics.dll) exceeds ¼ gigabyte, the logarithm returned by BigInteger.Log is incorrect. In the calculation, an Int32 accidentally overflows and therefore it may become negative.

Please also see http://stackoverflow.com/questions/14402877/ for a discussion of the problem.

This is seen in .NET 4.5 and .NET 4.0.
Sign in to post a comment.
Posted by Immo [MSFT] on 2/21/2013 at 7:24 AM
Thank you for your feedback. We are not going to be able to address this issue in our next release due to other priorities.

Regards,
Immo Landwerth
.NET Framework team
Posted by Immo [MSFT] on 2/21/2013 at 7:23 AM
Thank you for your feedback. We are not going to be able to address this issue in our next release due to other priorities.

Regards,
Immo Landwerth
.NET Framework team
Posted by Helen [MSFT] on 1/20/2013 at 8:28 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Macy [MSFT] on 1/18/2013 at 2:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)