search for: dcc888

...is based on, but it's not even implemented there. Short answer, without special casing this in magic ways, i wouldn't expect this to get fixed anytime soon. If we fixed assume in one of the ways i thought about, like bodik's extended ssa: http://homepages.dcc.ufmg.br/~fernando/classes/dcc888/ementa/slides/RangeAnalysis.pdf You would at least see that the load result is used by an assume, and could go look at that assume and so something with it. Currently, it's a few steps away. In the current scheme, assumes just float in air, and so it can be hard to see what their effects tou...

...; Short answer, without special casing this in magic ways, i wouldn't >> expect this to get fixed anytime soon. >> >> If we fixed assume in one of the ways i thought about, like bodik's >> extended ssa: >> >> http://homepages.dcc.ufmg.br/~fernando/classes/dcc888/ementa/slides/RangeAnalysis.pdf >> >> You would at least see that the load result is used by an assume, and >> could go look at that assume and so something with it. Currently, it's a >> few steps away. >> >> In the current scheme, assumes just float in air,...

I understood your modules and I see as them can be used in LNT. But there are some question about old features. 1. With Makefiles we can write pass and collect some statistics. There was an example of branch pass. Metrics can be collected by @-$(LOPT) -load dcc888$(SHLIBEXT) -branch-counter -stats \ -time-passes -disable-output $< 2>>$@ in makefile. In report file we write how data should be parsed. Can we do same things now with cmake+lit? 2. As I saw in LNT code there is no opportunity to compile but not execute tests. Some metrics cab be...

...org> wrote: > > I understood your modules and I see as them can be used in LNT. But there are some question about old features. > 1. With Makefiles we can write pass and collect some statistics. There was an example of branch pass. Metrics can be collected by > @-$(LOPT) -load dcc888$(SHLIBEXT) -branch-counter -stats \ -time-passes -disable-output $< 2>>$@ > in makefile. In report file we write how data should be parsed. Can we do same things now with cmake+lit? This question hits several points at once: - Collecting metrics at compiletime: The Makefiles have defin...

As of llvm 3.8, the early CSE pass seems to remove llvm.assume intrinsics. Is this the expected behavior? I've attached as small-ish example of this happening in my production code. $ opt -early-cse before-early-cse.ll -S > after-early-cse.ll Note the use of the assume intrinsic indicating that the loaded value %channels equals 3. In a later pass I replace the load instruction with

> On May 25, 2016, at 1:54 AM, Elena Lepilkina via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi Matthias, > > Thank you for your answer. > But can you answer for some more questions? > First of all, now LNT uses make-style of running tests and parse results from result csv file. Are there any plans to go to cmake? As James already said "lnt runtest

Hi Matthias, Thank you for your answer. But can you answer for some more questions? First of all, now LNT uses make-style of running tests and parse results from result csv file. Are there any plans to go to cmake? As I understood lit will run and collect all metrics, but there is no opportunity to make any settings for choosing what metrics I would like to collect. Test reports files allow to