2 ms·

> But since the premise is that any difference breaks the code, Not any. > will it work the exact same way across different devices Yes, where they run IEEE

> But since the premise is that any difference breaks the code, Not any. > will it work the exact same way across different devices Yes, where they run IEEE FP format.

Dylan16807 2y ago
> Not any. Just about any. It's pretty difficult to write code where changing the rounding of the last couple bits breaks it (as happens if you use wider types during the calculation), but other changes don't break it. What real code have you seen with that behavior?
- chrisjj 2y ago
  > but other changes don't break it. Why should that be a requirement? Obviously the driver can make other changes that can break any code.
  - Dylan16807 2y ago
    > Why should that be a requirement? Originally I said "the premise is that any difference breaks the code". You replied with "Not any." That is where the requirement comes from, your own words. This is your scenario, and you said not all differences would break the hypothetical code. This is your choice. Are we talking about code where any change breaks it (like a seeded/reproducible RNG), or are we talking about code where there are minor changes that don't break it but using extra precision breaks it? (I expect this category to be super duper rare)
    - chrisjj 2y ago
      > Originally I said "the premise is that any difference breaks the code". > You replied with "Not any." > That is where the requirement comes from, your own words. I wasn't stating a requirement. I was disputing your report of the premise. > or are we talking about code where there are minor changes that don't break it but using extra precision breaks it? Yup.
      - Dylan16807 2y ago
        > > or are we talking about code where there are minor changes that don't break it but using extra precision breaks it? > Yup Then I will ask again, have you ever seen code that falls into this category? I haven't. And an RNG would not fall into this category.

> But since the premise is that any difference breaks the code, Not any. > will it work the exact same way across different devices Yes, where they run IEEE FP format.

Dylan16807 2y ago

> Not any. Just about any. It's pretty difficult to write code where changing the rounding of the last couple bits breaks it (as happens if you use wider types during the calculation), but other changes don't break it. What real code have you seen with that behavior?

chrisjj 2y ago
> but other changes don't break it. Why should that be a requirement? Obviously the driver can make other changes that can break any code.
- Dylan16807 2y ago
  > Why should that be a requirement? Originally I said "the premise is that any difference breaks the code". You replied with "Not any." That is where the requirement comes from, your own words. This is your scenario, and you said not all differences would break the hypothetical code. This is your choice. Are we talking about code where any change breaks it (like a seeded/reproducible RNG), or are we talking about code where there are minor changes that don't break it but using extra precision breaks it? (I expect this category to be super duper rare)
  - chrisjj 2y ago
    > Originally I said "the premise is that any difference breaks the code". > You replied with "Not any." > That is where the requirement comes from, your own words. I wasn't stating a requirement. I was disputing your report of the premise. > or are we talking about code where there are minor changes that don't break it but using extra precision breaks it? Yup.
    - Dylan16807 2y ago
      > > or are we talking about code where there are minor changes that don't break it but using extra precision breaks it? > Yup Then I will ask again, have you ever seen code that falls into this category? I haven't. And an RNG would not fall into this category.