StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10407036
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-05-02T02:44:58.540
FavoriteCount
0
LastActivityDate
2012-05-02T02:44:58.540
LastEditDate
LastEditorUserId
0
OwnerUserId
1051115
ParentId
968435
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
If your program is parallelized, as it might be to run on a quad core, then it may well be non-deterministic. Imagine that you have 4 processors adding a floating point value to the same memory location. Then you might get <pre><code>(((InitialValue+P1fp)+P2fp)+P3fp)+P4fp </code></pre> or <pre><code>(((InitialValue+P2fp)+P3fp)+P1fp)+P4fp </code></pre> or any of the other possible orderings. Heck, you might even get <pre><code> InitialValue+(P2fp+P3fp)+(P1fp+P4fp) </code></pre> if the compiler is good enough. Unfortunately, floating point addition is not commutative or associative. Real number arithmetic is, but floating point is not, because of rounding, overflow, and underflow. Because of this, parallel FP computation is often non-deterministic. "Often", because programs that look like <pre><code> on each processor while( there is work to do ) { get work calculate result add to total } </code></pre> will be non-deterministic, because the amount of time that each takes may vary widely - you can't predict the order of operations. (Worse if the threads interact.) But not always, because there are styles of parallel programming that are deterministic. Of course, what many folks who care about determinism do is work in integer or fixed point to avoid the problem. I am particularly fond of superaccumulators, 512, 1024, or 2048 bit numbers that floating point numbers can be added to, without suffering rounding errors. <hr> As for a single threaded application: the compiler may rearrange the code. Different compilations may give different answers. But any particular binary should be deterministic. Unless... you are working in a dynamic language. That performs optimizatuions that reorder the FP computations, that vary over time. Or unless... really long shot: Itanium had some features, like the ALAT, that made even single threaded coded non-deterministic. You are unlikely to be affected by these.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat could cause a deterministic process to generate floating point errors
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USKrazy Glew
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.