Displaying 5 results from an estimated 5 matches for "get_foo".
2011 Dec 07
0
[LLVMdev] Generating DWARF information that pretends an outparam is the return value
Unfortunately this is what I'm already doing, and it's not working. I
drew inspiration from a disassembly of a program that showed that
struct foo {
int a; float b; char buf[80];
}
struct foo get_foo(void) {
foo f = { 5, 2.5 };
return f;
}
would turn into
define void @get_foo(%struct.foo* sret %agg.result) nounwind ssp {
...
call void @llvm.memcpy.p0i8.p0i8.i64(i8* %2, i8* %3, i64 88, i32 4,
i1 false), !dbg !24
ret void, !dbg !25
}
with similar metadata to what you wrote. I tried...
2011 Dec 07
2
[LLVMdev] Generating DWARF information that pretends an outparam is the return value
On Dec 6, 2011, at 4:13 PM, Devang Patel wrote:
> Hi Josh,
>
> On Dec 4, 2011, at 9:33 PM, Josh Matthews wrote:
>
>> I'm working on generating debug information for Rust, and I'm
>> currently stumped on how to generate DWARF output via LLVM that will
>> correctly represent this (eg. when exiting from foo2(), I'd like to
>> see "Value returns
2007 Sep 03
1
API survey results & update
...hand will be made available to all methods
which accept point or size arguments:
textctrl.set_size [200, 100]
# or
textctrl.size = [200, 100]
3) Getter and setter methods can be accessed using the naming style more
common in Ruby as well as that more common in C++/Java:
* Instance methods like get_foo can be accessed as foo
* Instance methods like set_foo can be accessed as foo=
* Instance methods like is_foo can be accessed as foo?
2020 Jun 03
5
[cfe-dev] [RFC] Refactor Clang: move frontend/driver/diagnostics code to LLVM
> On Jun 2, 2020, at 4:21 PM, comex via cfe-dev <cfe-dev at lists.llvm.org> wrote:
>
> While this is a different area of the codebase, another thing that
> would benefit greatly from being moved out of Clang is function call
> ABI handling. Currently, that handling is split awkwardly between
> Clang and LLVM proper, forcing frontends that implement C FFI to
> either
2006 Sep 07
2
A little bit of sugar
...to complement rather than replace the
existing syntax (so you can run existing wxRuby code with them).
You can require ''wx_sugar/all'' to load all the behaviours, or select
particular ones including
* ''accessors'' : creates ruby-style accessors (foo instead of get_foo,
foo= instead of set_foo, foo? instead of is_foo). If there''s a consensus
that we want to follow WxPython in doing this, I''ll submit a patch that
implements this at the C API level.
* ''keyword_constructors'' : For example, Wx::Button.new(:label => ''...