Displaying 4 results from an estimated 4 matches for "internal_metadata".
2012 Jun 05
2
[LLVMdev] alloc_size metadata
...ion may
> be deleted if the function gets inlined (i.e., nulled in the
> metadata), but I don't think we can workaround that problem. This is
> a best-effort approach, anyway.
>
>
> To avoid these functions being removed, I propose a new linkage
> type. Something like internal_metadata (or hopefully a better name).
> This linkage would mean that a function can only be removed in
> codegen, and if it has no users. The difference to internal linkage,
> is that internal functions with no users can be deleted at any time.
Is it possible to determine which functions are refe...
2012 Jun 05
0
[LLVMdev] alloc_size metadata
...leted if the function gets inlined (i.e., nulled in the
>> metadata), but I don't think we can workaround that problem. This is
>> a best-effort approach, anyway.
>>
>>
>> To avoid these functions being removed, I propose a new linkage
>> type. Something like internal_metadata (or hopefully a better name).
>> This linkage would mean that a function can only be removed in
>> codegen, and if it has no users. The difference to internal linkage,
>> is that internal functions with no users can be deleted at any time.
>
> Is it possible to determine whi...
2012 Jun 04
0
[LLVMdev] alloc_size metadata
...ameters of the allocation function may
be deleted if the function gets inlined (i.e., nulled in the
metadata), but I don't think we can workaround that problem. This is a
best-effort approach, anyway.
To avoid these functions being removed, I propose a new linkage type.
Something like internal_metadata (or hopefully a better name). This
linkage would mean that a function can only be removed in codegen, and
if it has no users. The difference to internal linkage, is that
internal functions with no users can be deleted at any time.
So, what do you think about this new proposal? I guess it a...
2012 Jun 02
5
[LLVMdev] alloc_size metadata
Hi Hal,
On 02/06/12 14:28, Hal Finkel wrote:
> On Sat, 02 Jun 2012 09:56:30 +0200
> Duncan Sands<baldrick at free.fr> wrote:
>
>> Hi Hal,
>>
>>> To do bounds checking you need two things: First you need to know
>>> the bounds (this requires tracking calls to allocation functions),
>>> and then you need to look at memory accesses. My guess is