I did not have Trump killing the Fortran 77 compiler industry on my bingo card.

(The F77 compiler industry is entirely subsidised by the DOE, because they have a codebase written in F77 that, by law, cannot be modified unless its revalidated. It can be revalidated only by modelling a nuclear bomb exploding then actually exploding one and seeing whether they are the same. They would love to move it to F90 or newer but can't as long as the test-ban treaty is in effect.)

@david_chisnall cannot be validated against the output of the F77 tool chain?

@zygoon @david_chisnall Agreed, OP’s assertion would indicate you can’t even do maintenance releases of F77 without “revalidating”. Generally frowned upon to add a nuclear explosion to your CI

EDIT: I’m not saying OP is wrong, it just seems really odd and I’d like to see a citation or something that explains it. Quick google turned up nothing for me

@neilk @zygoon Citation: I used to work on a F77 compiler, these people were our customer. They gave the worst bug reports:

Them: The code does not work!
Us: Can you provide a reduced test case?
Then: We will produce one and get it declassified.

Six months pass

Them: Here is the test case!
Us: The test case does not trigger the bug.
Them: Oh. Right. We had to remove that bit when we declassified it.

@iterativesec @david_chisnall @neilk @zygoon

I have the honor of finding a bug in SQLite. It was in a government data set, we were a government contractor.

We had to basically craft a “parallel construction” that triggered the bug. That was fun.

(To SQLite’s credit, it was fixed the next day and the code detected the invalid state and aborted rather than corrupt our data. Such lovely code.)