search for: alacconvert

Hi Tim, Thanks for the explanation. The above code snippets is actually extracted by bugpoint from MultiSource/Applications/ALAC/encode/alacconvert-encode.test. I get a different result if I cast the pointer to int and mask away the lower two bits and cast the int back to pointer. While casting pointer to int and back to pointer do not cause any problem. Thanks Hongbin On Fri, Dec 16, 2016 at 12:14 PM, Tim Northover <t.p.northover at gmai...

Hi Hongbin, On 16 December 2016 at 12:22, Hongbin Zheng <etherzhhb at gmail.com> wrote: > Thanks for the explanation. The above code snippets is actually extracted by > bugpoint from MultiSource/Applications/ALAC/encode/alacconvert-encode.test. > I get a different result if I cast the pointer to int and mask away the > lower two bits and cast the int back to pointer. While casting pointer to > int and back to pointer do not cause any problem. It's quite possible there's some undefined behaviour in ALAC that&...

Hi Hongbin, On 16 December 2016 at 11:57, Hongbin Zheng via llvm-dev <llvm-dev at lists.llvm.org> wrote: > We have an "align 4" in the StoreInst. Does this mean > 1) the address 'A' should be aligned to 4 bytes? > 2) the lower 2 bits of 'A' should be always 0? Yes, these are both the same. It means the compiler will assume those facts when reasoning about

...-18.603319977103 Benchmarks/mediabench/adpcm/rawdaudio/rawda 0.0022 0.0018 -18.181818181818 Benchmarks/FreeBench/fourinarow/fourinarow 0.2457 0.2018 -17.867317867317 Benchmarks/Prolangs-C++/family/family 0.0006 0.0005 -16.666666666666 Applications/ALAC/encode/alacconvert-encode 0.0314 0.0264 -15.923566878980 Benchmarks/MiBench/security-rijndael/securi 0.0243 0.0207 -14.814814814814 Benchmarks/mediabench/gsm/toast/toast 0.0174 0.0149 -14.367816091954 Benchmarks/Prolangs-C++/shapes/shapes 0.0007 0.0006 -14.28571...

Andy and I briefly discussed this the other day, we have not yet got chance to list a detailed pass order for the pre- and post- IPO scalar optimizations. This is wish-list in our mind: pre-IPO: based on the ordering he propose, get rid of the inlining (or just inline tiny func), get rid of all loop xforms... post-IPO: get rid of inlining, or maybe we still need it, only

...13491866|239.61| 9831357120|413.65|1.134860168|239.62| 9831359440|413.65| |Bitcode/Benchmarks/Halide/local_laplacian/halide_local_laplacian.test | 40|2.071047626|38767595010|2.072455961| -0.07|38767396810| 0|2.068001419| 0.15|38767469541| 0| |MultiSource/Applications/ALAC/decode/alacconvert-decode.test | 1000|0.010544763| 91421419|0.010553151| -0.08| 91421603| 0|0.010542988| 0.02| 91421603| 0| |MultiSource/Applications/ALAC/encode/alacconvert-encode.test | 1000|0.023955411| 212117365|0.023962085| -0.03| 212117343| 0| 0.02398535|...