Re: smtgcc translation validation

2024-08-19 Thread Krister Walfridsson via Gcc
On Sun, 18 Aug 2024, Gerald Pfeifer wrote: On Sat, 30 Sep 2023, Krister Walfridsson via Gcc wrote: I have now released the new implementation for translation validation I talked about at the GNU Tools Cauldron last week: https://github.com/kristerw/smtgcc Wouldn't it be appropriate/ni

Re: smtgcc translation validation

2024-08-18 Thread Gerald Pfeifer
On Sat, 30 Sep 2023, Krister Walfridsson via Gcc wrote: > I have now released the new implementation for translation validation I talked > about at the GNU Tools Cauldron last week: > https://github.com/kristerw/smtgcc Wouldn't it be appropriate/nice to promote this a bit more

smtgcc translation validation

2023-09-30 Thread Krister Walfridsson via Gcc
I have now released the new implementation for translation validation I talked about at the GNU Tools Cauldron last week: https://github.com/kristerw/smtgcc /Krister

Re: Translation validation

2022-09-20 Thread Krister Walfridsson via Gcc
On Wed, 14 Sep 2022, Richard Biener wrote: Note that the folding/peephole optimizations done early can be avoided when you separate opportunities in the source to multiple statements, like change int a, b; a = b + 1 - b; to a = b + 1; a = a - b; note that parts of the folding optimizations

Re: Translation validation

2022-09-13 Thread Richard Biener via Gcc
On Tue, Sep 13, 2022 at 11:33 PM Krister Walfridsson via Gcc wrote: > > I have implemented a tool for translation validation (similar to Alive2 > for LLVM). The tool takes GIMPLE IR for two functions and checks that the > second is a refinement of the first. That is, > * The re

Translation validation

2022-09-13 Thread Krister Walfridsson via Gcc
I have implemented a tool for translation validation (similar to Alive2 for LLVM). The tool takes GIMPLE IR for two functions and checks that the second is a refinement of the first. That is, * The returned value is the same for both functions for all input that does not invoke undefined