Sylvestre's blog - Derniers Commentaires le Status of LLVM in Debian https://sylvestre.ledru.info/blog/?disp=comments fr-FR http://backend.userland.com/rss 60 foo [Visiteur] en réponse à: Status of LLVM in Debian Tue, 17 May 2011 03:07:25 +0000 foo [Visiteur] c29174@https://sylvestre.ledru.info/blog/ <p>Can we haz deez toolz?</p> <p><a href="http://blog.llvm.org/2011/05/what-every-c-programmer-should-know_14.html" class="linebreak" rel="nofollow ugc">http://blog.llvm.org/2011/05/what-every-c-programmer-should-know_14.html</a></p> <p>Dey make DACA better.</p> Can we haz deez toolz?

http://blog.llvm.org/2011/05/what-every-c-programmer-should-know_14.html

Dey make DACA better.

]]> https://sylvestre.ledru.info/blog/2011/05/17/status_of_llvm_in_debian#c29174 Joe Buck [Visiteur] en réponse à: Status of LLVM in Debian Tue, 17 May 2011 02:22:57 +0000 Joe Buck [Visiteur] c29173@https://sylvestre.ledru.info/blog/ <p>Since the only differences between gcc version x.y.z and x.y.z+1 are bug fixes, it&#8217;s probably safe if the version number differs only in the third part. But if y is different, that spells serious trouble (crashes or bad code could be expected), since there will be much larger internal changes. If you&#8217;re going to allow version mismatch, I would recommend only allowing a mismatch in the third part.</p> Since the only differences between gcc version x.y.z and x.y.z+1 are bug fixes, it’s probably safe if the version number differs only in the third part. But if y is different, that spells serious trouble (crashes or bad code could be expected), since there will be much larger internal changes. If you’re going to allow version mismatch, I would recommend only allowing a mismatch in the third part.

]]> https://sylvestre.ledru.info/blog/2011/05/17/status_of_llvm_in_debian#c29173