search for: fdump

Dear LLVM-Mailing-List, inspired by a Mail some days ago I wondered, if it is possible to determine the offset of a pointer to a specific vtable of a class via the llvm::Module. For this I created two classes A & B which both used virtual functions. Now I created a class C which inherits A & B. In my simple understanding of C++ class 'C' would have two additional vtable pointers

Hi, Can someone help me with how to dump the vtable and the vptr addresses within it? Thanks, Dami -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170529/5dc7e058/attachment.html>

...atched/cipher/blowfish: Makefile diff -r tinc-0.3/cipher/blowfish/bf_cfb64.c tinc-0.3-patched/cipher/blowfish/bf_cfb64.c 60a61 > #include <syslog.h> 75a77 > diff -r tinc-0.3/cipher/cipher.c tinc-0.3-patched/cipher/cipher.c 19a20,21 > #include <stdio.h> > 32a35,36 > void fdump(FILE *, char *, int); > 46c50,53 < --- > if (debug_lvl > 3) { > syslog(LOG_ERR, "about to blowfish_cfb64"); > syslog(LOG_ERR, "length in packet: %ld", len); > } 47a55,57 > if (debug_lvl > 3) { > syslog(LOG_ERR, "done blowfis...

Installing odesolve in Raqua 1.8.0 or 1.8.1 under MacOSX gives the following message: Warning message: Installation of package odesolve had non-zero exit status in: install.packages(ui.pkgs, CRAN = getOption(where), lib = .libPaths()[1]) Moreover, in the source of odesolve is no makefile. Does anyone know how to get a proper installation? Maartje

...inter type gfortran -fpic -g -O2 -c cfode.f -o cfode.o gfortran -fpic -g -O2 -c dgbfa.f -o dgbfa.o gfortran -fpic -g -O2 -c dgbsl.f -o dgbsl.o gfortran -fpic -g -O2 -c dgefa.f -o dgefa.o gfortran -fpic -g -O2 -c dgesl.f -o dgesl.o gfortran -fpic -g -O2 -c ewset.f -o ewset.o gfortran -fpic -g -O2 -c fdump.f -o fdump.o gfortran -fpic -g -O2 -c fnorm.f -o fnorm.o gfortran -fpic -g -O2 -c i1mach.f -o i1mach.o gfortran -fpic -g -O2 -c intdy.f -o intdy.o gfortran -fpic -g -O2 -c j4save.f -o j4save.o gfortran -fpic -g -O2 -c lsoda.f -o lsoda.o gcc -std=gnu99 -I/usr/share/R/include -I/usr/share/R/include -...

Only Clang really knows the original structure layout. You can pass '-Xclang -fdump-record-layouts', though, to see the layout during compilation. The DICompositeType metadata produced when compiling with debug info might contain enough information to describe the original layout. On Wed, Dec 28, 2016 at 6:44 PM, Hong Hu via llvm-dev < llvm-dev at lists.llvm.org> wrote:...

...of the class A, the map will tell that in fact it is accessing the originally 3rd member (i1). Any suggestion? Regards, Hu Hong On 29 December 2016 at 10:50, Reid Kleckner <rnk at google.com> wrote: > Only Clang really knows the original structure layout. You can pass > '-Xclang -fdump-record-layouts', though, to see the layout during > compilation. The DICompositeType metadata produced when compiling with > debug info might contain enough information to describe the original layout. > > On Wed, Dec 28, 2016 at 6:44 PM, Hong Hu via llvm-dev < > llvm-dev at l...

...gt; > Great work! > > I think the following statement in the paper is not true: "gcov relies on > debug > information which is less accurate in optimized builds." GCC's gcov > implementation does not rely on debugging information. This can be > verified with > -fdump-debug: `gcc --coverage -fdump-debug -c a.c` dumps an empty > a.c.*.debug > file. > > After a second look at https://gcc.gnu.org/onlinedocs/gcc/Gcov-Intro.html#Gcov-Intro, it seems that I misunderstood why it is recommended to disable optimizations in gcov. You are right. This should be...

...char *srname, int *info) so xerbla_ is defined with two arguments. However, gfortran passes string lengths as hidden arguments. You can see this by compiling the small example $ cat xer.f SUBROUTINE FOO INTEGER INFO CALL XERBLA ('FOO', INFO) END $ gfortran -c -fdump-tree-original xer.f $ cat xer.f.004t.original foo () { integer(kind=4) info; xerbla (&"FOO"[1]{lb: 1 sz: 1}, &info, 3); } so here we have three arguments. This mismatch is flagged by -Wlto-type-mismatch, which, for example, yields print.c:1120:12: note: type 'void'...

On Mon, 11 Sep 2006, [UTF-8] Rafael Esp?ndola wrote: > I am trying to build llvm-gcc4 on a amd64. I had to add the attached > patch to get the build system to select the correct library. Now the Applied. > build fails while compiling a code that has __builtin_va_copy. The > attached test.i fails with: > > cc1: ../../trunk/gcc/llvm-convert.cpp:443: llvm::Value* >

Thanks, Eli. Next question is how to get the layout of the original C++ class from LLVM IR? Regards, Hu Hong On 29 December 2016 at 01:57, Friedman, Eli <efriedma at codeaurora.org> wrote: > On 12/28/2016 5:41 AM, Hong Hu via llvm-dev wrote: > > Hi all, > > I'm writing a pass to understand the memory access to C++ class members. > For each GetElementPtr instruction,

I am trying to build llvm-gcc4 on a amd64. I had to add the attached patch to get the build system to select the correct library. Now the build fails while compiling a code that has __builtin_va_copy. The attached test.i fails with: cc1: ../../trunk/gcc/llvm-convert.cpp:443: llvm::Value* TreeToLLVM::Emit(tree_node*, llvm::Value*): Assertion `(isAggregateType(((exp)->common.type)) == (DestLoc

...arently what happens is that the loop header is duplicated, which results in two entry points for the loop. Since this could obstruct subsequent loop optimizations, it might be interesting to further investigate this behavior. To show the problem, I have included an example from libmad: llvm-gcc -fdump-tree-all -O0 -I. -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -O0 -m32 -I/usr/include -c bit.c -o Output/bit.bc -emit-llvm opt -print-cfg Output/bit.bc -o test.bc -f dot -o test.ps -Tps cfg.mad_bit_crc.dot In the CFG of mad_bit_crc(), the second while loop is entered from two other basic blocks. From w...

## TL;DR We introduce bcov, an open-source binary-level coverage analysis tool [1]. The details are discussed in our paper [2], which is accepted to ESEC/FSE'20. bcov statically instruments x86-64 ELF binaries without compiler support. It features several techniques that allow it to achieve high performance, transparency, and flexibility. For example, running "make

...ned with two arguments. > > However, gfortran passes string lengths as hidden arguments. > You can see this by compiling the small example > > $ cat xer.f > ????? SUBROUTINE FOO > ????? INTEGER INFO > ????? CALL XERBLA ('FOO', INFO) > ????? END > $ gfortran -c -fdump-tree-original xer.f > $ cat xer.f.004t.original > foo () > { > ? integer(kind=4) info; > > ? xerbla (&"FOO"[1]{lb: 1 sz: 1}, &info, 3); > } > > so here we have three arguments. This mismatch is flagged > by -Wlto-type-mismatch, which, for example, yie...

This morning we got a fault management message from one of our production servers stating that a fault in one of our pools had been detected and fixed. Looking into the error using fmdump gives: fmdump -v -u 90ea244e-1ea9-4bd6-d2be-e4e7a021f006 TIME UUID SUNW-MSG-ID Oct 22 09:29:05.3448 90ea244e-1ea9-4bd6-d2be-e4e7a021f006 FMD-8000-4M Repaired

Hi, try adding some alias analysis to the pipeline: see examples in llvm/test/Analysis/MemorySSA/*.ll for example assume.ll has ; RUN: opt -aa-pipeline=basic-aa -passes='print<memoryssa>,verify<memoryssa>' without basic-aa the memory ssa will safely assume that the stores to %a and %d alias which may be proven disjoint by one of the alias analyses. On Thu, Aug 9, 2018 at 8:37