#compilertesting search results

WEBINAR: SuperTest Compiler Test and Validation Suite. Register here: bit.ly/3zknZ7P Tuesday, September 24th at 10:00 AM or 6:00 PM (CEST) #testenvironments #compilertesting #safetyqualification


WEBINAR: SuperTest Compiler Test and Validation Suite. Click here to register: bit.ly/3zknZ7P Tuesday, September 24th at 10:00 AM or 6:00 PM (CEST) #testenvironments #compilertesting #safetyqualification


New SuperTest update features native Windows support and requirements traceability for C and C++ language specifications: #C #CPlusPlus #Compilertesting #SuperTest bit.ly/2EAErnl For Free Trail : bit.ly/2NLruHY


For a typical compiler, more than half of the source code is optimization related. That is why all that code must be pretty robust and well tested. Are you sure that is the case? #Compiler #SourceCode #CompilerTesting #SuperTest #SolidSandsPartner bit.ly/2Tloc0f


"...we don't check compiler output", says a former director for Meta. The implied 0% test coverage does explain some things.

I believe this new model in Claude Code is a glimpse of the future we're hurtling towards, maybe as soon as the first half of next year: software engineering is done. Soon, we won't bother to check generated code, for the same reasons we don't check compiler output.



Codex should ALWAYS test it’s work, all work should compile, shouldn’t have to direct it to do these things. Include the ability to test in the browser/test the UI


Compiler output is checked very rarely if 'ever' (or even impossible w JS) for probably 95% of development. In game dev of HFT or small chunks of perf sensitive code people might check compiler output.

"for the same reason we don't check compiler output" AHAHAHAHA who's gonna tell him



But we do check complier output. It’s called “testing.”


This is never going to happen. Also, we do check compiler output. Not by hand, but by verifying the compiler produces the correct functionality. There's no way to do that with AI code because the results are too complex and who writes the test cases? Still more AI?


I recently created a small compiler to revise and practise my basics ..... This project really helped me refresh core concepts Try it- compiler-project-gzrs.vercel.app


Is your compiler a boy or a MAN? Created by Donald Knuth, it’s a test to check if recursion is implemented properly. Originally written in ALGOL 60, a precursor to C, but can adapt to nearly any language. It really stresses the stack and heap, pushing insane call depths:


Made a custom test tool for my compiler that runs all the tests for all the platforms and generates a matrix report. I've got like 30 tests on 5 different platforms already, so it'll only get worse without some automation.

tsoding's tweet image. Made a custom test tool for my compiler that runs all the tests for all the platforms and generates a matrix report. I've got like 30 tests on 5 different platforms already, so it'll only get worse without some automation.

WEBINAR: SuperTest Compiler Test and Validation Suite. Register here: bit.ly/3zknZ7P Tuesday, September 24th at 10:00 AM or 6:00 PM (CEST) #testenvironments #compilertesting #safetyqualification


WEBINAR: SuperTest Compiler Test and Validation Suite. Click here to register: bit.ly/3zknZ7P Tuesday, September 24th at 10:00 AM or 6:00 PM (CEST) #testenvironments #compilertesting #safetyqualification


Developers using dynamic languages write tests to verify their code executes properly Developers using strongly-typed languages have a test tool already available. It's called a compiler and it was built by some of the smartest people on the planet


Compiler Explorer now has a new and much improved control flow graph tool, check it out here! godbolt.org/z/vczGT6T9c @CompileExplore Big thanks to folks from the @cutter_re project for their thorough documentation and help with solving layout challenges!

JeremyRifkin's tweet image. Compiler Explorer now has a new and much improved control flow graph tool, check it out here! godbolt.org/z/vczGT6T9c @CompileExplore
Big thanks to folks from the @cutter_re project for their thorough documentation and help with solving layout challenges!

Compiler Explorer @CompileExplore now has an llvm optimization pipeline viewer <godbolt.org/z/xa7q4GToz>! Thanks @partouf for the code review and help getting it production ready

JeremyRifkin's tweet image. Compiler Explorer @CompileExplore now has an llvm optimization pipeline viewer &amp;lt;godbolt.org/z/xa7q4GToz&amp;gt;! Thanks @partouf for the code review and help getting it production ready

My compiler team at Shopify is experimenting with writing performance tests by asserting the shape of the compiler graph rather than by measuring time. Can therefore run in CI without needing dedicated hardware, and results deterministic.

ChrisGSeaton's tweet image. My compiler team at Shopify is experimenting with writing performance tests by asserting the shape of the compiler graph rather than by measuring time. Can therefore run in CI without needing dedicated hardware, and results deterministic.
ChrisGSeaton's tweet image. My compiler team at Shopify is experimenting with writing performance tests by asserting the shape of the compiler graph rather than by measuring time. Can therefore run in CI without needing dedicated hardware, and results deterministic.
ChrisGSeaton's tweet image. My compiler team at Shopify is experimenting with writing performance tests by asserting the shape of the compiler graph rather than by measuring time. Can therefore run in CI without needing dedicated hardware, and results deterministic.

We just shipped beta 100 of the compiler to The People. That's approximately 1 beta per week since we started. I personally packed up and shipped all 100 of these. The compiler is currently 87,050 lines of code, and compiles programs as quickly as it ever did.


Just sent out beta #50 of the compiler. We are now up to 76 beta participants. We shipped an average of one beta every 8.5 days. Current compiler size: 56,128 lines.


slightly hacky way to test whether all your #golang tests at least compile after a big refactor, without actually running them: $ go test --exec=/bin/true ./...


Experimental implementation of C++ pattern matching (wg21.link/P1371) is available on Compiler Explorer! A silly fizz buzz example: godbolt.org/z/fdd5j4 Thank you to @brunosy for the on-going implementation work and @lenary for the Compiler Explorer deployment. #cpp

mcypark's tweet image. Experimental implementation of C++ pattern matching (wg21.link/P1371) is available on Compiler Explorer!

A silly fizz buzz example: godbolt.org/z/fdd5j4

Thank you to @brunosy for the on-going implementation work and @lenary for the Compiler Explorer deployment.

#cpp

Modern compilers check your code for many kinds of errors. Could we “compile” writing, beyond the level of spelling and grammar checking? For example, highlight a sentence to get an estimate of whether it’s considered true by a given knowledge base.


Big news!! You can now run your code snippets in Compiler Explorer: godbolt.org/z/ZCwZK8 Have fun! Let us know what you get up to! Please file issues and requests on the GitHub tracker (github.com/mattgodbolt/co…)


No results for "#compilertesting"
No results for "#compilertesting"
Loading...

Something went wrong.


Something went wrong.


United States Trends