Displaying 5 results from an estimated 5 matches for "usincg".
2013 Apr 16
2
[LLVMdev] Passing DW_TAG_typedef as the type to DIBuilder's createFunction
...t; and what is correct/good:
>
> typedef int foo(int);
> foo bar;
>
> is 'bar' a function of type "int(int)" or a function of type "foo"
> which is a typedef of type "int(int)". I suppose it could be the
> latter, in which case we should be usincg/allowing a function's type
> to be a typedef.
It's not going to come up with anything since bar is unused :)
I've been unable to come up with any way to use foo as a type for a
function. If you can come up with one...
-eric
2013 Apr 16
0
[LLVMdev] Passing DW_TAG_typedef as the type to DIBuilder's createFunction
...n GCC debug info, Clang debug info,
and what is correct/good:
typedef int foo(int);
foo bar;
is 'bar' a function of type "int(int)" or a function of type "foo"
which is a typedef of type "int(int)". I suppose it could be the
latter, in which case we should be usincg/allowing a function's type
to be a typedef.
2013 Apr 10
2
[LLVMdev] Passing DW_TAG_typedef as the type to DIBuilder's createFunction
Hi Eric,
On 10/04/13 00:20, Eric Christopher wrote:
> On Tue, Apr 9, 2013 at 1:53 AM, Duncan Sands <baldrick at free.fr> wrote:
>> Hi David, I'm seeing an assertion failure when passing this node
>>
>> !{i32 786454, metadata <badref>, metadata <badref>, metadata !"fn_t", i32
>> 5, i64 0, i64 0, i64 0, i32 0, metadata <badref>} ;
2013 Apr 16
0
[LLVMdev] Passing DW_TAG_typedef as the type to DIBuilder's createFunction
...>>
>> typedef int foo(int);
>> foo bar;
>>
>> is 'bar' a function of type "int(int)" or a function of type "foo"
>> which is a typedef of type "int(int)". I suppose it could be the
>> latter, in which case we should be usincg/allowing a function's type
>> to be a typedef.
>
> It's not going to come up with anything since bar is unused :)
Sure, so make it used...
But then we still don't emit anything about the function (& neither does GCC).
So make it a member function (so we are forced to e...
2013 Apr 17
2
[LLVMdev] Passing DW_TAG_typedef as the type to DIBuilder's createFunction
...ypedef int foo(int);
>>> foo bar;
>>>
>>> is 'bar' a function of type "int(int)" or a function of type "foo"
>>> which is a typedef of type "int(int)". I suppose it could be the
>>> latter, in which case we should be usincg/allowing a function's type
>>> to be a typedef.
>>
>> It's not going to come up with anything since bar is unused :)
>
> Sure, so make it used...
>
Sure.. but...
> But then we still don't emit anything about the function (& neither does GCC).
>...