search for: differenceengin

Hi all, I'm considering adding debug metadata logic to llvm-diff, but it looks like some heavy refactoring will be needed to do so. Who's the owner of it? There is too much logic in DifferenceEngine, classes being declared in the cpp file, sub-classes of DifferenceEngine that could be used by the metadata diff, but with the current style (FunctionDifferenceEngine(*this)) will be hard to share. I propose creating more files to split up the logic and use the appropriate h/cpp split, even if th...

On Feb 28, 2011, at 3:36 AM, Renato Golin wrote: > I'm considering adding debug metadata logic to llvm-diff, but it looks > like some heavy refactoring will be needed to do so. Who's the owner > of it? Me. > There is too much logic in DifferenceEngine, classes being declared in > the cpp file, sub-classes of DifferenceEngine that could be used by > the metadata diff, but with the current style > (FunctionDifferenceEngine(*this)) will be hard to share. > > I propose creating more files to split up the logic and use the > appro...

...bcanalyzer (without symbols) llvm[2]: Linking Release+Asserts executable llvm-mc (without symbols) llvm[2]: ======= Finished Linking Release+Asserts Executable llvm-bcanalyzer (without symbols) make[2]: Leaving directory `/local/csaba/LLVM/build-release/tools/llvm-bcanalyzer' llvm[2]: Compiling DifferenceEngine.cpp for Release+Asserts build llvm[2]: Compiling ExtractFunction.cpp for Release+Asserts build /local/csaba/LLVM/build-release/tools/llvm-mc/Release+Asserts/llvm-mc.o: In function `main': llvm-mc.cpp:(.text+0x2879): undefined reference to `LLVMInitializeAArch64TargetInfo' llvm-mc.cpp:(.tex...

I want to run a bunch of optimizations, iteratively, that is keep running until things stop changing (to make sure all optimization opportunities are taken). As far as I know, there is no way to copy a module or compare modules by value, so it occurs to me that a practical solution might be to take the hash code of the module and see if that changes. A problem is that hash algorithms are designed

On 24 August 2010 00:19, John McCall <rjmccall at apple.com> wrote: > Note that llvm-diff is meant solely as a tool for debugging IR;  pretty much all > details of the output, from formatting to actual information, is subject to change. Hi John, This is fine, I'll not use it on any production system nor rely on its output for anything, it's also mainly for IR debugging. I

...es. > I noticed you have virtual functions but non-virtual destructor on > Oracle and Consumer. It might not matter much at this stage, as > they're not extended, but it's good to fix it. ;) I'll "fix" it on the day it seems like a good idea to layer a API on top of DifferenceEngine that takes ownership of an Oracle of unknown type. I'm not sure why that would ever happen. :) John.

> On Jul 23, 2016, at 1:53 PM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > On Sat, Jul 23, 2016 at 7:48 PM, Piotr Padlewski <prazek at google.com <mailto:prazek at google.com>> wrote: >> How big is your project? >> LTO eats RAM even faster than chrome. For example linking clang with LTO >>

...eaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/tools/llvm-mc' llvm[2]: Compiling Miscompilation.cpp for Release+Asserts build llvm[2]: Compiling DiffLog.cpp for Release+Asserts build make[2]: Entering directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/tools/macho-dump' llvm[2]: Compiling DifferenceEngine.cpp for Release+Asserts build llvm[2]: Compiling macho-dump.cpp for Release+Asserts build llvm[2]: Linking Release+Asserts executable macho-dump (without symbols) llvm[2]: Compiling OptimizerDriver.cpp for Release+Asserts build llvm[2]: Compiling llvm-diff.cpp for Release+Asserts build llvm[2]: Co...