search for: liballocator

Hi Vedant, > I enjoyed reading through your EuroLLVM slides and OOPSLA paper. > Detecting the creation of contract-violating pointers is an > interesting idea, and your paper demonstrates that the checking can > be comprehensive and effective. Glad you enjoyed them. :-) > However, I have concerns about the quality of diagnostics, the > complexity of the driver, and about

Hi all, Some of you might remember that at EuroLLVM last year in Barcelona, Chris Diamand and I gave a talk about Clang/libcrunch, a run-time checking system which can be thought of as another flavour of sanitizer. It checks pointer casts, using run-time type information. Roughly the check is that the pointer really points to an instance of the target type, though there are refinements to

Dear Michael, The symbols that are said undefined by the compiler live in libAllocator.a. That file should be in Release/lib/, do you have it? It is possible that the compiler has linking order problems. What is the version of your gcc? You can try changing the link order of the make command by editing tools/vmkit/Makefile. Also, you should know that the GC of vmkit does not...

Hi, I can't seem to get VMKit to compile correctly. I'm on a 64 bit Jaunty system. I compiled llvm and llvm-gcc from the subversion source no problem, but when I try to compile VMKit I get some issue with GCAllocator: /home/mmwu/Download/llvm$ ./configure /home/mmwu/Download/llvm$ make ENABLE_OPTIMIZED=1 /home/mmwu/Download/llvm$ make ENABLE_OPTIMIZED=1 install ...

...INED_ON_WINDOWS) \ diff --git a/plugins/data/Makefile.am b/plugins/data/Makefile.am index de6e80bb..f4684915 100644 --- a/plugins/data/Makefile.am +++ b/plugins/data/Makefile.am @@ -62,6 +62,7 @@ nbdkit_data_plugin_la_LDFLAGS = \ nbdkit_data_plugin_la_LIBADD = \ $(top_builddir)/common/allocators/liballocators.la \ $(top_builddir)/common/utils/libutils.la \ + $(LINK_LIBNBDKIT_ON_WINDOWS) \ $(GNUTLS_LIBS) \ $(NULL) diff --git a/plugins/eval/Makefile.am b/plugins/eval/Makefile.am index 4ea8d7d4..4b2aa598 100644 --- a/plugins/eval/Makefile.am +++ b/plugins/eval/Makefile.am @@ -65,6 +65,7 @@ nbdkit_...

Hi everyone, At EuroLLVM, Chandler and I chatted about the design for a potential TBAA sanitizer. Here's my attempt to summarize: C/C++ have type-based aliasing rules, and LLVM's optimizer can exploit these given TBAA metadata added by Clang. Roughly, a pointer of given type cannot be used to access an object of a different type (with, of course, certain exceptions). Unfortunately,

Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw This is the port to Windows using native Windows APIs (not MSYS or Cygwin). This patch series is at the point where it basically now works. I can run the server with the memory plugin, and access it remotely using guestfish, creating filesystems and so on without any apparent problems. Nevertheless there are many

On 04/07/2017 09:26 AM, Stephen Kell wrote: >> At EuroLLVM, Chandler and I chatted about the design for a potential >> TBAA sanitizer. Here's my attempt to summarize: >> >> C/C++ have type-based aliasing rules, and LLVM's optimizer can exploit >> these given TBAA metadata added by Clang. Roughly, a pointer of given >> type cannot be used to access an

Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw-nolib After a lot of work I have made the port to Windows work without using a separate library. Instead, on Windows only, we build an "import library" (library of stubs) which resolves references to nbdkit_* functions in the main program and fixes up the plugin, basically the first technique outlined in