Displaying 3 results from an estimated 3 matches for "vtble".
Did you mean:
vtable
2012 Jan 30
0
[LLVMdev] [RFC] Module Flags Metadata
On Jan 27, 2012, at 5:00 PM, Dan Gohman wrote:
> Not all of these are miscompiles,
None I'd say, may be TBAA.
> but the point is that valid but
> naive optimizations can cause them to be actively misleading
... but not cause mis-compilation. Note, optimization passes are free to update info conveyed through MDNodes, if they want to. The "optional to update" while still
2012 Jan 28
2
[LLVMdev] [RFC] Module Flags Metadata
On Jan 27, 2012, at 3:40 PM, Devang Patel wrote:
> [ removing cfe-dev from the cc list ]
>
> On Jan 27, 2012, at 1:31 PM, Dan Gohman wrote:
>
>> On Jan 27, 2012, at 11:20 AM, Devang Patel wrote:
>>
>>>
>>> On Jan 26, 2012, at 2:10 PM, Dan Gohman wrote:
>>>
>>>> On Jan 26, 2012, at 12:54 PM, Devang Patel wrote:
2012 Jan 30
2
[LLVMdev] [RFC] Module Flags Metadata
...I'd say, may be TBAA.
Then you missed value ranges and fpaccuracy.
Anyway, here are some examples of optimizations which aren't
implemented yet, but which have been seriously considered: metadata
to mark C++ copy constructors, to allow the optimizer to eliminate
them. Metadata to mark C++ vtble pointers, to facilitate
devirtualization. Metadata to implement loop pragmas, like
"ivdep". Metadata to annotate floating-point operations compiled
with flags like -ffinite-math-only. All could be made to cause
miscompiles by valid optimizations.
>
>> but the point is that vali...