search for: bilateral_grid

...set in two groups, and checks that [opt -debug-pass=Arguments] reports the same sequences when called with -O3 and the individual arguments. If a file name is provided, it also checks that the outputs are the same (or in our case, different). Many real files fail to pass this test, for instance bilateral_grid.bc: <https://github.com/llvm/llvm-test-suite/blob/master/Bitcode/Benchmarks/Halide/bilateral_grid/bilateral_grid.bc> The diffs are very large even in text mode, and include lots of code. I'm puzzled again. Any clue on the behavior of opt is very welcome. :) Cheers, Sébastien Michell...

...iation shows. I'll withdraw the performance claim until I can get consistent results (changed subject line), apologies for the confusion. What I can still show easily is that the code generated by these two methods is different (which is already weird). For a simple example, grab a copy of bilateral_grid.bc: <https://github.com/llvm/llvm-test-suite/blob/master/Bitcode/Benchmarks/Halide/bilateral_grid/bilateral_grid.bc> Then you can generate my sequences with [opt -O3 -debug-pass=Arguments] and diff the outputs. Please see the attached script. The differences seem to be mainly on variabl...

...ps, and checks that [opt -debug-pass=Arguments] reports the same sequences when called with -O3 and the individual arguments. If a file name is provided, it also checks that the outputs are the same (or in our case, different). >> >> Many real files fail to pass this test, for instance bilateral_grid.bc: >> >> <https://github.com/llvm/llvm-test-suite/blob/master/Bitcode/Benchmarks/Halide/bilateral_grid/bilateral_grid.bc> >> >> The diffs are very large even in text mode, and include lots of code. >> >> I'm puzzled again. Any clue on the behavior o...

...erformance claim until I can get consistent results > (changed subject line), apologies for the confusion. > > What I can still show easily is that the code generated by these two > methods is different (which is already weird). For a simple example, > grab a copy of bilateral_grid.bc: > > > <https://github.com/llvm/llvm-test-suite/blob/master/Bitcode/Benchmarks/Halide/bilateral_grid/bilateral_grid.bc> > > Then you can generate my sequences with [opt -O3 -debug-pass=Arguments] > and diff the outputs. Please see the attached script. >...

Hello list, This is a follow-up from a question I asked last month. I'm evaluating the performance of two pass sequences that resemble (but are not) -O3. With -O3, -debug-pass=Structure prints several independent blocks that seem to represent several calls to opt. I focused on two of these blocks, say S1 and S2, and compared the following optimization methods: 1. Executing them

Hi Mehdi, Thank you for mentioning this tool, I was looking for something like this. By default the analyzer produces identical output on both files, but a complete -dump shows that the storage order of the symbol table is different. This would explain why text files are not affected: the symbols are used directly in text form so there is no need for this table. I suppose that settles the

...truct. | Seconds |Diff,%| |Diff,%| Seconds |Diff,%| |Diff,%| |------------------------------------------------------------------------------|------|-----------|-----------|-----------|------|-----------|------|-----------|------|-----------|------| |Bitcode/Benchmarks/Halide/bilateral_grid/halide_bilateral_grid.test | 40| 2.56518256|54828688896|2.552624706| 0.49|54828702561| 0|2.565364148| -0.01|54828691567| 0| |Bitcode/Benchmarks/Halide/blur/halide_blur.test | 40|3.854254085|50498796318| 1.13491866|239.61| 9831357120|413.65|1.13...