Displaying 4 results from an estimated 4 matches for "mdkindid".
2009 Sep 16
1
[LLVMdev] [proposal] Extensible IR metadata
...debug info prompted this, thoughts welcome:
>> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt
>
> Here is partial initial implementation.
> Thoughts ?
setHasMetadata probably shouldn't be public, like there's no way to
directly set HasValueHandle.
I'd make the MDKindId type (or typedef) now so it's obvious what those
"unsigned"s mean.
Should the metadata name->id map be per-context or global? I think
it's unlikely people will be registering these things during
compilation, so we can afford the overhead of a lock, and making it
global helps w...
2009 Sep 16
0
[LLVMdev] [proposal] Extensible IR metadata
On Fri, Sep 11, 2009 at 9:57 AM, Chris Lattner <clattner at apple.com> wrote:
> Devang's work on debug info prompted this, thoughts welcome:
> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt
Here is partial initial implementation.
Thoughts ?
-
Devang
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mdn.diff
Type: application/octet-stream
2009 Sep 11
12
[LLVMdev] [proposal] Extensible IR metadata
Devang's work on debug info prompted this, thoughts welcome:
http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt
-Chris
2009 Sep 11
0
[LLVMdev] [proposal] Extensible IR metadata
...nt in different
executions.
Since the optimizers may want more methods over time, but we don't
really want to require users to extend their wrappers, we should say
that all wrappers must inherit from a particular type. I'd name this
type "MDKind" and rename the proposed MDKind to MDKindID. Then we can
add defaults to MDKind over time. Nothing needs to be virtual since
these types are all used as template arguments.
We could either use a global list of IDs for the MDKinds or have
separate lists for each Context. StaticTypeId can only provide a
global list, so giving each Context its...