Displaying 4 results from an estimated 4 matches for "_zn".
Did you mean:
_n
2019 Jan 06
2
LLVM IR linking separate function definitions in header files in single IR
...want to have a single IR with all the
> definitions of the called functions that are implemented in header files".
>
> The IR you're sending contains all the code defined in the header. The
> line you are posting above is present multiple times, for example in the
> function _ZN9__gnu_cxx13new_allocatorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEE8allocateEmPKv
>
>
>
>> but in IR there is no malloc...
>>
>
> Do you have calls to malloc in the source code?
>
>
>> how can i identify such instructions in IR...by call void @_ZN??...
2019 Jan 01
4
LLVM IR linking separate function definitions in header files in single IR
Hello,
I have different codes with separate files with functions implemented. I
want to view all function definitions/ instructions in single IR. I am able
to do this by llvm-link for codes which have definition implemented in .c
files...
But there are some codes which have definitions instructions in header
files. These functions are called from .c file. I want to have a single IR
with all the
2006 Oct 12
9
Newbie question: 28000+ files for 25000+ records?
Hi
Obviously my question is, is that normal? To have so many files? I was
indexing 6 string fields from 25000+ model records (all of the same
model). The index appears to be working. I guess I was expecting a few
hundred files after optimzing, not more files that records indexed.
Please understand I am brand spanking new to Lucene, Ferret, and AaF.
I was using acts_as_ferret with
:fields
2014 Feb 21
12
[LLVMdev] asan coverage
>
>
>
> We may need some additional info.
What kind of additional info?
> I haven't put a ton of thought into
> this, but I'm hoping we can either (a) use debug info as is or add some
> extra (valid) debug info to support this, or (b) add an extra
> debug-info-like section to instrumented binaries with the information we
> need.
>
I'd try this data