Displaying 10 results from an estimated 10 matches for "arg8".
Did you mean:
arg
2005 Sep 03
2
Problem with swig?
Take a look at the generated code from ListBox.cpp:
static VALUE
_wrap_new_wxListBox__SWIG_0(int argc, VALUE *argv, VALUE self) {
VALUE arg1 ;
wxWindow *arg2 = (wxWindow *) 0 ;
wxWindowID arg3 ;
wxPoint *arg4 = 0 ;
wxSize *arg5 = 0 ;
int arg6 ;
wxString *arg7 ;
long arg8 ;
wxValidator *arg9 = 0 ;
wxString *arg10 = 0 ;
wxListBox *result;
wxString *arr6 ;
arg8 has no default value!
Here''s the definition from the .h file:
wxListBox(wxWindow* parent , wxWindowID id , const wxPoint& pos =
wxDefaultPosition, const wxSize& size =...
2013 Dec 06
1
Paging in waves.
...E})is),10)
same =>
n,ExecIf($[${ISNULL(${ARG5})}=0]?Page(${ARG5},n(${RECORDED_FILE})is),10)
same =>
n,ExecIf($[${ISNULL(${ARG6})}=0]?Page(${ARG6},n(${RECORDED_FILE})is),10)
same =>
n,ExecIf($[${ISNULL(${ARG7})}=0]?Page(${ARG7},n(${RECORDED_FILE})is),10)
same =>
n,ExecIf($[${ISNULL(${ARG8})}=0]?Page(${ARG8},n(${RECORDED_FILE})is),10)
same =>
n,ExecIf($[${ISNULL(${ARG9})}=0]?Page(${ARG9},n(${RECORDED_FILE})is),10)
same =>
n,ExecIf($[${ISNULL(${ARG10})}=0]?Page(${ARG10},n(${RECORDED_FILE})is)10)
same => n,Set(MUTEAUDIO(all)=off)
same => n,Playback(goodbye)
same =&...
2012 Sep 04
2
[PATCH] valgrind: Support for ioctls used by Xen toolstack processes.
...arguments to that hypercall and the
toolstack only initialises the arguments which are used. However
there is no space in the DEFN_PRE_TEMPLATE prototype to allow this to
be communicated from syswrap-xen.c back to syswrap-linux.c. Since a
hypercall can have at most 5 arguments I have hackily stolen ARG8 for
this purpose.
---
configure.in | 19 +
coregrind/Makefile.am | 8 +-
coregrind/m_debuginfo/debuginfo.c | 9 +
coregrind/m_syswrap/priv_syswrap-xen.h | 10 +
coregrind/m_syswrap/syswrap-linux.c | 107 ++++-
coregrind/m_syswrap/syswra...
2013 Nov 10
3
[LLVMdev] loop vectorizer erroneously finds 256 bit vectors
...32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-elf"
define void @main(i64 %arg0, i64 %arg1, i64 %arg2, i1 %arg3, i64 %arg4,
float* noalias %arg5, float* noalias %arg6, float* noalias %arg7,
double* noalias %arg8) {
entrypoint:
br i1 %arg3, label %L0, label %L1
L0: ; preds = %entrypoint
%0 = add nsw i64 %arg0, %arg4
%1 = add nsw i64 %arg1, %arg4
br label %L2
L1: ; preds = %entrypoint
br label %L2
L2...
2013 Nov 10
0
[LLVMdev] loop vectorizer erroneously finds 256 bit vectors
...128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64-S128"
>
> target triple = "x86_64-unknown-linux-elf"
>
> define void @main(i64 %arg0, i64 %arg1, i64 %arg2, i1 %arg3, i64
> %arg4, float* noalias %arg5, float* noalias %arg6, float* noalias
> %arg7, double* noalias %arg8) {
> entrypoint:
> br i1 %arg3, label %L0, label %L1
>
> L0: ; preds = %entrypoint
> %0 = add nsw i64 %arg0, %arg4
> %1 = add nsw i64 %arg1, %arg4
> br label %L2
>
> L1: ;...
2013 Nov 10
2
[LLVMdev] loop vectorizer erroneously finds 256 bit vectors
...64-f80:128:128-n8:16:32:64-S128"
>>
>> target triple = "x86_64-unknown-linux-elf"
>>
>> define void @main(i64 %arg0, i64 %arg1, i64 %arg2, i1 %arg3, i64 %arg4,
>> float* noalias %arg5, float* noalias %arg6, float* noalias %arg7, double*
>> noalias %arg8) {
>> entrypoint:
>> br i1 %arg3, label %L0, label %L1
>>
>> L0: ; preds = %entrypoint
>> %0 = add nsw i64 %arg0, %arg4
>> %1 = add nsw i64 %arg1, %arg4
>> br label %L2
>>
>> L1:...
2013 Nov 10
0
[LLVMdev] loop vectorizer erroneously finds 256 bit vectors
...28:128-n8:16:32:64-S128"
>
> target triple = "x86_64-unknown-linux-elf"
>
> define void @main(i64 %arg0, i64 %arg1, i64 %arg2, i1 %arg3,
> i64 %arg4, float* noalias %arg5, float* noalias %arg6, float*
> noalias %arg7, double* noalias %arg8) {
> entrypoint:
> br i1 %arg3, label %L0, label %L1
>
> L0: ; preds =
> %entrypoint
> %0 = add nsw i64 %arg0, %arg4
> %1 = add nsw i64 %arg1, %arg4
> br label %L2
&...
2008 Jan 18
33
LatencyTop
I see Intel has released a new tool. Oh, it requires some patches to
the kernel to record
latency times. Good thing people don''t mind patching their kernels, eh?
So who can write the equivalent latencytop.d the fastest? ;-)
http://www.latencytop.org/
--
cburgess at qnx.com
2014 Feb 21
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
Thank you, Clayton. It works now!
Our debugger server responds
"name:J28;generic:fp;bitsize:32;encoding:uint;format:hex;gcc:60;dwarf:60".
And I also set other "generic" attributes like sp, pc, ra, arg1~arg8 to
related registers.
I dig a little and find llvm dwarf generator uses
TargetRegisterInfo::getFrameRegister() to obtain frame base, and uses
TargetFrameLowering::getFrameIndexReference() to obtain frame base as well
as frame offset of a variable.
lldb is OK to check value of variable including b...
2014 Feb 20
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
Thank you, Clayton. This is very helpful.
We use the LLDB specific GDB remote extensions, and our debugger server
supports "qRegisterInfo" package. "reg 0x3c" is the frame pointer.
In the example mentioned above, we have SP = FP - 40 for current call frame.
And variable "a" is stored at address (FP + -24) from asm instruction [FP +
-24] = R3;;
Thus we can conclude