Path: csiph.com!xmission!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Hans-Peter Diettrich Newsgroups: comp.compilers Subject: Re: Parser Reversed Date: Tue, 13 Mar 2018 11:23:02 +0100 Organization: Compilers Central Lines: 34 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <18-03-053@comp.compilers> References: <18-03-038@comp.compilers> <18-03-040@comp.compilers> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="60258"; mail-complaints-to="abuse@iecc.com" Keywords: parse Posted-Date: 13 Mar 2018 15:35:08 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:1999 Am 11.03.2018 um 15:08 schrieb Matt P. Dziubinski: > On 3/11/2018 08:32, Hans-Peter Diettrich wrote: >> A grammar can be used to *check* for valid sentences of a language, but >> it also can be used to *create* valid sentences. For a pretty printer or >> decompiler test I need a sentence generator for logical expressions. For >> now the language can be restricted to AND, OR, variables and (kind of) >> parentheses. Later on NOT and XOR can be added. RPN is one alternative >> for the "kind of parentheses", eliminating the need for a specific >> operator precedence. >> >> Now I'm looking for possible implementations of such a generator, in >> addition to my own ideas. So far the output can be anything, e.g. source >> code or machine code, or some tree (AST...). >> >> Any ideas or references to such projects? > > Hi! > > Csmith comes to mind: https://embed.cs.utah.edu/csmith/ Thanks for all the links :-) > * "Effect-Driven QuickChecking of Compilers" (notably, the following > goes substantially further than relying solely on the grammar grammar by > making use of the type system -- more in the paper): > > Code (Effect-Driven Compiler Tester): https://github.com/jmid/efftester > Paper: http://janmidtgaard.dk/papers/Midtgaard-al%3AICFP17-full.pdf > Talk: https://podcasts.ox.ac.uk/effect-driven-quickchecking-compilers Here I'm absolutely lost with the notation :-( DoDi