Displaying 3 results from an estimated 3 matches for "r209015".
Did you mean:
209015
2014 Jul 30
2
[LLVMdev] Inconsistent third field in global_ctors (was Re: [llvm] r214321 - UseListOrder: Visit global values)
...ou should be able to just reject it.
Looking a little deeper, it's not "old-style" exactly; rejecting this
isn't trivial.
- According to LangRef, the third field is optional [1].
[1]: http://llvm.org/docs/LangRef.html#the-llvm-global-ctors-global-variable
- It was added in r209015 to support comdat keys.
- The helper functions `llvm::appendToGlobalCtors()` and
`llvm::appendToGlobalDtors()` (in ModuleUtils.cpp) will by default
set up the two-field version.
- Despite the field being optional (and the API defaulting to the
short version), the BitcodeReader aut...
2014 Jul 31
2
[LLVMdev] Inconsistent third field in global_ctors (was Re: [llvm] r214321 - UseListOrder: Visit global values)
...not "old-style" exactly; rejecting this
> > isn't trivial.
> >
> > - According to LangRef, the third field is optional [1].
> >
> > [1]:
> http://llvm.org/docs/LangRef.html#the-llvm-global-ctors-global-variable
> >
> > - It was added in r209015 to support comdat keys.
> >
> > - The helper functions `llvm::appendToGlobalCtors()` and
> > `llvm::appendToGlobalDtors()` (in ModuleUtils.cpp) will by default
> > set up the two-field version.
> >
> > - Despite the field being optional (and the API d...
2014 Jul 31
2
[LLVMdev] Inconsistent third field in global_ctors (was Re: [llvm] r214321 - UseListOrder: Visit global values)
...this
>>>> isn't trivial.
>>>>
>>>> - According to LangRef, the third field is optional [1].
>>>>
>>>> [1]: http://llvm.org/docs/LangRef.html#the-llvm-global-ctors-global-variable
>>>>
>>>> - It was added in r209015 to support comdat keys.
>>>>
>>>> - The helper functions `llvm::appendToGlobalCtors()` and
>>>> `llvm::appendToGlobalDtors()` (in ModuleUtils.cpp) will by default
>>>> set up the two-field version.
>>>>
>>>> - Despite...