Displaying 4 results from an estimated 4 matches for "call_expr".
2012 Sep 13
1
[LLVMdev] Parsing C++ template parameters using cindex.py
...column 1>
result TypeKind.INVALID
kind CursorKind.TEMPLATE_REF
type
kind TypeKind.INVALID
xdata 0
data 48201424 75 4106544
children
cursor None
location <SourceLocation file 'testfile.cpp', line 11, column 11>
result TypeKind.INVALID
kind CursorKind.CALL_EXPR
type
kind TypeKind.UNEXPOSED
xdata 0
data 48356112 48357480 4106544
children
cursor test_struct
location <SourceLocation file 'testfile.cpp', line 12, column 9>
result TypeKind.INVALID
kind CursorKind.VAR_DECL
type
kind TypeKind.UNEXPOSED
xdata 0
data 48358032...
2006 Sep 02
0
[LLVMdev] gfortran calling convention
On Fri, 1 Sep 2006, Michael McCracken wrote:
> Here's what works now, and I have a separate test case for each of these:
>
> statement functions
> intrinsic functions (print, cos, etc)
> loops, goto statments
> scalarized array operations
> function calls with *no arguments*
> simple common blocks
Great!
> Function calls with more than one argument don't work.
2006 Sep 02
2
[LLVMdev] gfortran calling convention
The NIST F77 test suite doesn't seem to be compatible with gfortran at
all, so I had to work from my own sample codes, and generate test
cases from them.
Here's what works now, and I have a separate test case for each of these:
statement functions
intrinsic functions (print, cos, etc)
loops, goto statments
scalarized array operations
function calls with *no arguments*
simple common
2017 Jun 21
6
RFC: Cleaning up the Itanium demangler
...void print_left(stream& s) const override
+ {
+ s += callee;
+ s += "(";
+ for (size_t i = 0; i < nargs; ++i)
+ {
+ if (i) s += ", ";
+ args[i]->print(s);
+ }
+ s += ")";
+ }
+};
+
+class call_expr : public expr
+{
+ const node* callee;
+ const size_t nargs;
+ node** args;
+public:
+ call_expr(node* callee, size_t nargs, node** args)
+ : callee(callee), nargs(nargs), args(args) {}
+
+ void print_left(stream& s) const override
+ {
+ callee->print(s);...