News for hackers. Stuff that matters.
Re:The C standard formalized in Coq by nickpsecurity on Monday November 30, 2015 @11:18AM (#10650120)
So, you say they did a KCC-like thing in a theorem prover that could do more than KCC. Then, that it's just NIH syndrome against KCC? Seems contradictory. If anything, one would just have to tweak it on a per compiler basis to get it more toward how each implements that behavior. Then it becomes closer to what CompCert did but more flexible.

That's where I'd go. Extending KCC to do what a theorem prover could seems more challenging.

Re:The C standard formalized in Coq by conceit on Tuesday December 01, 2015 @09:02AM (#10655334)
That seems to be what he says, but after the first part he disregards that as not useful. Another comment points out following the standard is good for portabilities sake. Somehow, that all seems obvious to me.
Re:The C standard formalized in Coq by nickpsecurity on Tuesday December 01, 2015 @10:15AM (#10655880)
That was the build up. It led to the following statement and conclusion:

"For time when you want to prove abstractly to standard, this doesn't seem better than KCC. In short, this feels like Not Invented Here against KCC. Probably unfair characterization, but that's what it feels to me."

The obvious interpretation is commenter thinking KCC is better and (see NIH) the OP should've maybe done something with it instead...?

" Another comment points out following the standard is good for portabilities sake. Somehow, that all seems obvious to me."

You can follow the standard and be portable if you keep certain parts as options subject to interpretation/choice of the implementers. That's the so-called undefined behavior mostly.