search for: assemb

I am trying to understand the hello word assember example. This is my version: %str1 = internal constant [13 x sbyte] c"Hello World\0a\00" declare int %printf(sbyte*, ...) implementation ; Functions: int %main() { %str2 = getelementptr [13 x sbyte]* %str1, long 0, long 0 call int(sbyte*, ...) *%printf(sbyte* %str2) ret int...

...s on my Linux x86_64 Fedora box is: declare void @__ot_runtime_print_int(i8*, i32) define void @main() { entry: call void @__ot_runtime_print_int(i8* null, i32 12) br label %return return: ; preds = %entry ret void } LLVM magic turns this into the assember shown in the attached image. I am no expert but is seems to me that the address generated (0x8000012c1eea) for the __ot_runtime_print_int function is incorrect. As both nm and the debugger (kdbg) suggest that the address of the function in question is: 0x12c1eea. So why is the high bit of the...

...g/docs/GetElementPtr.html > > That will help you understand how it works. We wrote that document > specifically because this question comes up all the time. > > Reid. > > On Sun, 2006-11-12 at 11:13 -0800, Ram Bhamidipaty wrote: >> I am trying to understand the hello word assember example. This is >> my version: >> >> %str1 = internal constant [13 x sbyte] c"Hello World\0a\00" >> >> declare int %printf(sbyte*, ...) >> >> implementation ; Functions: >> >> int %main() { >> %str2 = getelementptr [13 x s...

...FAQ available here: http://llvm.org/docs/GetElementPtr.html That will help you understand how it works. We wrote that document specifically because this question comes up all the time. Reid. On Sun, 2006-11-12 at 11:13 -0800, Ram Bhamidipaty wrote: > I am trying to understand the hello word assember example. This is > my version: > > %str1 = internal constant [13 x sbyte] c"Hello World\0a\00" > > declare int %printf(sbyte*, ...) > > implementation ; Functions: > > int %main() { > %str2 = getelementptr [13 x sbyte]* %str1, long 0, long 0 >...

..., <16 x float> %a.79) align 8 { entry: %result.80 = fadd <16 x float> %a.78, %a.79 ret <18 x float> %result.80 } This works really well when the vector length (16 in the above) is an integer multiple of the SSE vector register width (4) resulting in the following assember code: vector_add_float: # @vector_add_float .Leh_func_begin0: # BB#0: # %entry addps %xmm4, %xmm0 addps %xmm5, %xmm1 addps %xmm6, %xmm2 addps %xmm7, %xmm3 ret However, when the vector length is increased to say 18, the gener...

...understand how it works. We wrote that document > >> specifically because this question comes up all the time. > >> > >> Reid. > >> > >> On Sun, 2006-11-12 at 11:13 -0800, Ram Bhamidipaty wrote: > >>> I am trying to understand the hello word assember example. This is > >>> my version: > >>> > >>> %str1 = internal constant [13 x sbyte] c"Hello World\0a\00" > >>> > >>> declare int %printf(sbyte*, ...) > >>> > >>> implementation ; Functions: > >...

...e zeroth, and in this case only, array of sbyte[13]. The next 0 actually indexes into the array of sbyte, so you are pointing at index 0, or pointing at the 'H' in "Hello World". Hope this helps, -- Robert. Ram Bhamidipaty wrote: > I am trying to understand the hello word assember example. This is > my version: > > %str1 = internal constant [13 x sbyte] c"Hello World\0a\00" > > declare int %printf(sbyte*, ...) > > implementation ; Functions: > > int %main() { > %str2 = getelementptr [13 x sbyte]* %str1, long 0, long 0 > call...

...t; >> That will help you understand how it works. We wrote that document >> specifically because this question comes up all the time. >> >> Reid. >> >> On Sun, 2006-11-12 at 11:13 -0800, Ram Bhamidipaty wrote: >>> I am trying to understand the hello word assember example. This is >>> my version: >>> >>> %str1 = internal constant [13 x sbyte] c"Hello World\0a\00" >>> >>> declare int %printf(sbyte*, ...) >>> >>> implementation ; Functions: >>> >>> int %main() { >...

Are you running in the JIT? If not, what assembler are you using? This looks like an issue with encoding the relative PC distance between the call site and the call entry. Notice that the call site is at a very high address (0x7fffff....) while the target is very low. x86_64 can't encode a full 64-bit immediate offset in the call instructi...

...works. We wrote that document >>>> specifically because this question comes up all the time. >>>> >>>> Reid. >>>> >>>> On Sun, 2006-11-12 at 11:13 -0800, Ram Bhamidipaty wrote: >>>>> I am trying to understand the hello word assember example. This is >>>>> my version: >>>>> >>>>> %str1 = internal constant [13 x sbyte] c"Hello World\0a\00" >>>>> >>>>> declare int %printf(sbyte*, ...) >>>>> >>>>> implementation ;...

...> entry: > %result.80 = fadd<16 x float> %a.78, %a.79 > ret<18 x float> %result.80 > } > > This works really well when the vector length (16 in the above) is > an integer multiple of the SSE vector register width (4) resulting > in the following assember code: > > vector_add_float: # @vector_add_float > .Leh_func_begin0: > # BB#0: # %entry > addps %xmm4, %xmm0 > addps %xmm5, %xmm1 > addps %xmm6, %xmm2 > addps %xmm7, %xmm3 > ret > > However,...

...ay I am currently passing call-specific parameters to the R script is via a text file created on the fly by the web service that is then loaded into a list: Ie. >Rscript script1.r par.file.txt foo <- commandArgs() par.file <- foo[1] The parameter text file "par.file.txt" assembed by the web server contains: 222222 #station number "River at River" #station name "ec" #name of wq variable to be plotted "EC"~(mu~s/cm) #axis label (in R plotmath expression) for RHS axis label And is read into a list called &quot...

Dear all, The background: as I didn't find a manual specifically directed towards debugging R code on a novice and intermediate level, I decided to write a student manual myself. I have some basic examples of errors (the classical interpunction and writing mistakes), but have the feeling that I miss quite some of the frequently occuring mistakes and messages. Therefore I'm looking around

Hi JM, Thanks for the earlier replies. I have tested it with quality 1,2&3 the result is not much different. Also I must tell you that I am using the armbe-linux-gcc compiler which does not suppoort arm5e-asm optimisations. I get lots of assember related errors. Is there any alternative? Will moving on to a board supported by arm-linux-gcc compiler ,to enable arm5e optimisation, help? Nav Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: Quality 0 has not been entirely converted to fixed-point, so it actually runs mu...

Hi, Thanks for pointing direction. As far, as I understand by reversing, logic, that I want to overwrite is digged into: lib/MC/MCSectionELF.cpp MCSectionELF::PrintSwitchToSection if (ShouldOmitSectionDirective(SectionName, MAI)) { OS << '\t' << getSectionName() << '\n'; return; } // otherwise print ".section" directive and then section

Re-post, as I think my last post didn't get through. Sorry, if somebody got it twice now Hi I run in the following make tests error and didn't find any solution to this. - This is a test on the localhost, so I guess, there is no man in the middle attack (hosts file is setup correctly, localhost points to 127.0.0.1) - I don't want to use protocol 1 anyway, so how can I skip

...; > Also, you will hit the "other language" problem sooner or > later. Robert's complaint is that he does not like black > boxes. But R itself is a black box. You cannot write R in R, > all the way down to the bottom. At the bottom is machine > code, and languages like assember, C, C++, FORTRAN and > their compilers provide "black box" wrappers for this. > > That is not a whimsical comment either -- all those discussions > about why 2 - sqrt(2)^2 is not equal to 0 come down to this > sort of issue. Sooner or later, if you really want to underst...

Hi, I'm new to Theora and would like to propose several performance optimization using advanced instructions in x86 CPUs (SSE2-SSE4.2). There are several source files in \x86 and \x86_vc which developed using inline assembler. However this cause several maintenance problems: 1) Need to sync gcc & msvc versions 2) Only 32bit environment is supported 3) No support for newer than MMX instruction sets My proposal is to replace all functions in assembly with compiler intrinsic which compiles into 1-2 assembly instruc...

...gh a "paravirt_ops" structure. Currently these are function implementations of native hardware: hypervisors will override the ops structure with their own variants. All the pv-ops functions are declared "fastcall" so that a specific register-based ABI is used, to make inlining assember easier. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Signed-off-by: Chris Wright <chrisw@sous-sol.org> =================================================================== --- a/arch/i386/Kconfig +++ b/arch/i386/Kconfig @@ -179,6 +179,17 @@ config X86_ES7000 should say N...

...gh a "paravirt_ops" structure. Currently these are function implementations of native hardware: hypervisors will override the ops structure with their own variants. All the pv-ops functions are declared "fastcall" so that a specific register-based ABI is used, to make inlining assember easier. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Signed-off-by: Chris Wright <chrisw@sous-sol.org> =================================================================== --- a/arch/i386/Kconfig +++ b/arch/i386/Kconfig @@ -179,6 +179,17 @@ config X86_ES7000 should say N...