Repository navigation
Replies: 2 comments
|
that sounds like a) a very expensive way to do it, if Claude has to translate them all (whereas Csmith itself is cheap), and b) not really exercise the language much by going thru only what C has. Likely better is to write GooseSmith :P Even that I am not sure is most effective, as fuzzing already does something similar. |
0 replies
|
GooseSmith... I like it but if the Goose compiler is what we are testing how do we verify GooseSmith output ? Csmith you can use a known good compiler against the compiler you're testing. We kind of have a chicken in the egg problem. Or is it a goose in the egg problem? 🙂
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Wouter van Oortmerssen ***@***.***>
Sent: Thursday, 05 November 2026 18:05:21
To: aardappel/goose ***@***.***>
Cc: mike tenuvahdesigns.com ***@***.***>; Author ***@***.***>
Subject: Re: [aardappel/goose] Validating Goose Compiler Idea (Discussion #237)
that sounds like a) a very expensive way to do it, if Claude has to translate them all (whereas Csmith itself is cheap), and b) not really exercise the language much by going thru only what C has.
Likely better is to write GooseSmith :P
Even that I am not sure is most effective, as fuzzing already does something similar.
—
Reply to this email directly, view it on GitHub<#237?email_source=notifications&email_token=AYMHAOXD7F5AL7MDRQCSE735XUWWDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGMYDSNBWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-19430946>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AYMHAOTHL37OTEKVLVPBPND5XUWWDAVCNFSNUABJKJSXA33TNF2G64TZHMYTGNJRG42DQOJSGM5UI2LTMN2XG43JN5XDWMJRGIZTMNBQHCQXMAQ>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/AYMHAOT7NBZ7BKEKVQN4ZC35XUWWDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGMYDSNBWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android<https://github.com/notifications/mobile/android/AYMHAOXFZMONAQQ4RF76TPD5XUWWDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGMYDSNBWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>. Download it today!
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi Wouter ! Thank you for all your work and effort to bring a new language into the world. Can I make a not well thought out suggestion to try an stress test the goose compiler ? Generate a bunch of horrible c programs using Csmith. Have Claude using a strict C -> Goose translator skill (mcp) / Agent translate the c program to Goose. Run the Goose and C programs side by side and compare the outputs. I know the weakness is the C -> Goose step but that also seems like a good piece of kit to have around. What do you think ?
Csmith (The Random Program Generator)
If you want a program that dynamically combines a massive breadth of C features to intentionally break compilers, Csmith is the answer.
• What it does: Instead of being one static program, Csmith is a tool that generates random, syntactically valid, and well-defined C programs.
• Why it's a nightmare for compilers: It aggressively uses complex combinations of pointers, arrays, deeply nested loops, structures, bitfields, and type castings. It was built specifically to find bugs in compilers like GCC and Clang by generating code so convoluted that it frequently triggers compiler crashes (Internal Compiler Errors) or uncovers optimization bugs.
All reactions