Displaying 7 results from an estimated 7 matches for "intconstants".
2020 Oct 01
3
Creating a global variable for a struct array
>The type you pass to GlobalVariable's constructor for that variable
should be "[10 x %struct.dlist]" because that's what you want storage
for. Then the GlobalVariable itself will be a Constant of type "[10 x
%struct.dlist]*".
Yes, I verified that this is the case.
I enabled assertions and the error seems to occur while creating GlobalVariable for both struct dhash
2009 Nov 30
2
[LLVMdev] DebugInfo and Metadata Store
On Thu, Nov 26, 2009 at 2:31 PM, Nick Lewycky <nicholas at mxc.ca> wrote:
> Hi Devang,
>
> Before I get to the contents of this particular patch, I have a higher-level
> design question. Why is metadata stored off the LLVMContext?
Why do we have FPConstants, IntConstants etc.. in LLVMContext ? :)
> That seems like
> the wrong place to me, this data is all specific to the particular module.
> Specifically, a single MDNode may not cross modules, and if a module is
> destroyed we should eliminate all the metadata that came with it.
Metadata is not connec...
2013 Dec 13
17
[Bug 10322] New: Slow Performance over Network rsync
https://bugzilla.samba.org/show_bug.cgi?id=10322
Summary: Slow Performance over Network rsync
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: core
AssignedTo: wayned at samba.org
ReportedBy: Joerg.Grube at Gmx.De
2020 Oct 01
2
Creating a global variable for a struct array
Thank you very much. The code to initialize h1 to non-zero values was what I was looking for.
It's almost working except for a type mismatch wrt dlist* llist field of h1.
dlist static_lst[10] = { {1, 5, NULL}, ... };
dhash h1[10] = {{"myfile.txt", static_lst}, ... };
Along the lines of the code you had sent, I created a GlobalVariable* llist of type [10 x %struct.dlist]* for the
2009 Nov 26
0
[LLVMdev] DebugInfo and Metadata Store
Hi Devang,
Before I get to the contents of this particular patch, I have a
higher-level design question. Why is metadata stored off the
LLVMContext? That seems like the wrong place to me, this data is all
specific to the particular module. Specifically, a single MDNode may not
cross modules, and if a module is destroyed we should eliminate all the
metadata that came with it.
So, why
2009 Nov 30
0
[LLVMdev] DebugInfo and Metadata Store
...26, 2009 at 2:31 PM, Nick Lewycky <nicholas at mxc.ca> wrote:
> > Hi Devang,
> >
> > Before I get to the contents of this particular patch, I have a
> higher-level
> > design question. Why is metadata stored off the LLVMContext?
>
> Why do we have FPConstants, IntConstants etc.. in LLVMContext ? :)
>
So you can build up Constants and Instructions before inserting them where
they'll be used. I suppose that sounds reasonable to do for metadata too.
> That seems like
> > the wrong place to me, this data is all specific to the particular
> module....
2009 Nov 25
3
[LLVMdev] DebugInfo and Metadata Store
Hi All,
Now, in llvm trunk we support custom metadata, which can be attached
with llvm instructions. One of the user is "debugging information".
This user is special (not just because it is in llvm svn tree:)
because whenever debug info is available, it is likely that
corresponding metadata is attached with almost all instructions. In
other words, usually it is all or nothing. This