search for: rinput

...following bit of >> TGSI code: >> >> COMP >> DCL SV[0], THREAD_ID[0] >> DCL TEMP[0], LOCAL >> DCL TEMP[1], LOCAL >> IMM UINT32 { 8, 0, 0, 0 } >> >> BGNSUB\n" >> UMUL TEMP[0], SV[0], IMM[0] >> LOAD TEMP[1].xy, RINPUT, TEMP[0] >> LOAD TEMP[0].x, RGLOBAL, TEMP[1].yyyy >> UADD TEMP[1].x, TEMP[0], -TEMP[1] >> STORE RGLOBAL.x, TEMP[1].yyyy, TEMP[1] >> RET >> ENDSUB >> >> >> Where by RINPUT and RGLOBAL get replaces by processing the &...

...>>> DCL SV[0], THREAD_ID[0] >>>> DCL TEMP[0], LOCAL >>>> DCL TEMP[1], LOCAL >>>> IMM UINT32 { 8, 0, 0, 0 } >>>> >>>> BGNSUB\n" >>>> UMUL TEMP[0], SV[0], IMM[0] >>>> LOAD TEMP[1].xy, RINPUT, TEMP[0] >>>> LOAD TEMP[0].x, RGLOBAL, TEMP[1].yyyy >>>> UADD TEMP[1].x, TEMP[0], -TEMP[1] >>>> STORE RGLOBAL.x, TEMP[1].yyyy, TEMP[1] >>>> RET >>>> ENDSUB >>>> >>>> >>>&...

...llo, I need a bit of handholding with R, specifically, with writing packages for it. I'm a systems programmer, and am, on the request of several users of our software, working on generating R interfaces. For starters, I've written the following R function (which compiles): SEXP myincr(SEXP Rinput) { // Returns input integer incremented by one int input; SEXP returner; PROTECT(Rinput = AS_NUMERIC(Rinput)); input = * INTEGER(Rinput); input++; PROTECT(returner = NEW_INTEGER(input)); Rprintf("Hey there\n"); return returner; } I've made this into a package, by dropping it into a...

...AD_ID[0] >>>>> DCL TEMP[0], LOCAL >>>>> DCL TEMP[1], LOCAL >>>>> IMM UINT32 { 8, 0, 0, 0 } >>>>> >>>>> BGNSUB\n" >>>>> UMUL TEMP[0], SV[0], IMM[0] >>>>> LOAD TEMP[1].xy, RINPUT, TEMP[0] >>>>> LOAD TEMP[0].x, RGLOBAL, TEMP[1].yyyy >>>>> UADD TEMP[1].x, TEMP[0], -TEMP[1] >>>>> STORE RGLOBAL.x, TEMP[1].yyyy, TEMP[1] >>>>> RET >>>>> ENDSUB >>>>> >&g...

...AD_ID[0] >>>>> DCL TEMP[0], LOCAL >>>>> DCL TEMP[1], LOCAL >>>>> IMM UINT32 { 8, 0, 0, 0 } >>>>> >>>>> BGNSUB\n" >>>>> UMUL TEMP[0], SV[0], IMM[0] >>>>> LOAD TEMP[1].xy, RINPUT, TEMP[0] >>>>> LOAD TEMP[0].x, RGLOBAL, TEMP[1].yyyy >>>>> UADD TEMP[1].x, TEMP[0], -TEMP[1] >>>>> STORE RGLOBAL.x, TEMP[1].yyyy, TEMP[1] >>>>> RET >>>>> ENDSUB >>>>> >&g...

...;>> >>> COMP >>> DCL SV[0], THREAD_ID[0] >>> DCL TEMP[0], LOCAL >>> DCL TEMP[1], LOCAL >>> IMM UINT32 { 8, 0, 0, 0 } >>> >>> BGNSUB\n" >>> UMUL TEMP[0], SV[0], IMM[0] >>> LOAD TEMP[1].xy, RINPUT, TEMP[0] >>> LOAD TEMP[0].x, RGLOBAL, TEMP[1].yyyy >>> UADD TEMP[1].x, TEMP[0], -TEMP[1] >>> STORE RGLOBAL.x, TEMP[1].yyyy, TEMP[1] >>> RET >>> ENDSUB >>> >>> >>> Where by RINPUT and RGLOBAL...

...nd if necessary clover) to start to work again. Currently the test_input_global() test uses the following bit of TGSI code: COMP DCL SV[0], THREAD_ID[0] DCL TEMP[0], LOCAL DCL TEMP[1], LOCAL IMM UINT32 { 8, 0, 0, 0 } BGNSUB\n" UMUL TEMP[0], SV[0], IMM[0] LOAD TEMP[1].xy, RINPUT, TEMP[0] LOAD TEMP[0].x, RGLOBAL, TEMP[1].yyyy UADD TEMP[1].x, TEMP[0], -TEMP[1] STORE RGLOBAL.x, TEMP[1].yyyy, TEMP[1] RET ENDSUB Where by RINPUT and RGLOBAL get replaces by processing the code with cpp and the following defines: #define RGLOBAL RES[32...

...would look like this: >> >> COMP >> DCL SV[0], THREAD_ID[0] >> DCL TEMP[0], LOCAL >> DCL TEMP[1], LOCAL >> IMM UINT32 { 0, 0, 0, 0 } >> IMM UINT32 { 4, 0, 0, 0 } >> IMM UINT32 { 128, 0, 0, 0 } >> >> BGNSUB >> LOAD TEMP[0].xy, RINPUT, IMM[0] >> UMUL TEMP[1].x, SV[0], IMM[1] >> UADD TEMP[0].x, TEMP[0], TEMP[1] >> UMUL TEMP[1].x, SV[0], IMM[2] >> UADD TEMP[0].y, TEMP[0], TEMP[1].xxxx >> LOAD TEMP[1].x, RGLOBAL, TEMP[0] >> LOAD TEMP[0].x, RGLOBAL,...

...x, TEMP1z STOREgis [TEMP1y], TEMP1x RET ENDSUB Working tgsi for this would look like this: COMP DCL SV[0], THREAD_ID[0] DCL TEMP[0], LOCAL DCL TEMP[1], LOCAL IMM UINT32 { 0, 0, 0, 0 } IMM UINT32 { 4, 0, 0, 0 } IMM UINT32 { 128, 0, 0, 0 } BGNSUB LOAD TEMP[0].xy, RINPUT, IMM[0] UMUL TEMP[1].x, SV[0], IMM[1] UADD TEMP[0].x, TEMP[0], TEMP[1] UMUL TEMP[1].x, SV[0], IMM[2] UADD TEMP[0].y, TEMP[0], TEMP[1].xxxx LOAD TEMP[1].x, RGLOBAL, TEMP[0] LOAD TEMP[0].x, RGLOBAL, TEMP[0].yyyy UADD TEMP[1].x, TEMP[0], -TEMP[1]...

...ently the test_input_global() test uses the following bit of > TGSI code: > > COMP > DCL SV[0], THREAD_ID[0] > DCL TEMP[0], LOCAL > DCL TEMP[1], LOCAL > IMM UINT32 { 8, 0, 0, 0 } > > BGNSUB\n" > UMUL TEMP[0], SV[0], IMM[0] > LOAD TEMP[1].xy, RINPUT, TEMP[0] > LOAD TEMP[0].x, RGLOBAL, TEMP[1].yyyy > UADD TEMP[1].x, TEMP[0], -TEMP[1] > STORE RGLOBAL.x, TEMP[1].yyyy, TEMP[1] > RET > ENDSUB > > > Where by RINPUT and RGLOBAL get replaces by processing the > code with cpp and the follow...

Hi there, Does anybody have experience in running jpeg device using xvfb-run on linux? I've been having sporadic problem with: /usr/X11/bin/xvfb-run /usr/bin/R --no-save < Rinput.txt, with error saying: error in X11 connection. Especially when I run it from a perl script. Is there a better way of doing this? or how can I fix the problem. Thanks in advance! David [[alternative HTML version deleted]]

...t the second dim when >> it's 0.) You don't even have to load these, you can use them as args >> directly anywhere you like (except as indirect addresses). >> >> The old code would actually take the supplied inputs, stick them into >> a constbuf, and then lower RINPUT accesses to load from that constbuf. >> I'm suggesting we cut out the middleman. >> >> By the way, another term for "constant buffer" is "uniform buffer", on >> the off chance it helps. Basically it's super-cached by the shader for >> values...

...ENDSUB > > Working tgsi for this would look like this: > > COMP > DCL SV[0], THREAD_ID[0] > DCL TEMP[0], LOCAL > DCL TEMP[1], LOCAL > IMM UINT32 { 0, 0, 0, 0 } > IMM UINT32 { 4, 0, 0, 0 } > IMM UINT32 { 128, 0, 0, 0 } > > BGNSUB > LOAD TEMP[0].xy, RINPUT, IMM[0] > UMUL TEMP[1].x, SV[0], IMM[1] > UADD TEMP[0].x, TEMP[0], TEMP[1] > UMUL TEMP[1].x, SV[0], IMM[2] > UADD TEMP[0].y, TEMP[0], TEMP[1].xxxx > LOAD TEMP[1].x, RGLOBAL, TEMP[0] > LOAD TEMP[0].x, RGLOBAL, TEMP[0].yyyy > UADD...

...ENDSUB > > Working tgsi for this would look like this: > > COMP > DCL SV[0], THREAD_ID[0] > DCL TEMP[0], LOCAL > DCL TEMP[1], LOCAL > IMM UINT32 { 0, 0, 0, 0 } > IMM UINT32 { 4, 0, 0, 0 } > IMM UINT32 { 128, 0, 0, 0 } > > BGNSUB > LOAD TEMP[0].xy, RINPUT, IMM[0] > UMUL TEMP[1].x, SV[0], IMM[1] > UADD TEMP[0].x, TEMP[0], TEMP[1] > UMUL TEMP[1].x, SV[0], IMM[2] > UADD TEMP[0].y, TEMP[0], TEMP[1].xxxx > LOAD TEMP[1].x, RGLOBAL, TEMP[0] > LOAD TEMP[0].x, RGLOBAL, TEMP[0].yyyy > UADD...

Hi, On 18-02-16 17:39, Ilia Mirkin wrote: > On Thu, Feb 18, 2016 at 9:45 AM, Hans de Goede <hdegoede at redhat.com> wrote: >> But this does not seem to be hooked up yet for nouveau. > > Samuel has patches. See > https://cgit.freedesktop.org/~hakzsam/mesa/log/?h=arb_compute_shader_v3 Cool, I will take a look at those. >> So some questions: >> -The commit by

...[0], CONST[0][1], etc -- it doesn't print the second dim when it's 0.) You don't even have to load these, you can use them as args directly anywhere you like (except as indirect addresses). The old code would actually take the supplied inputs, stick them into a constbuf, and then lower RINPUT accesses to load from that constbuf. I'm suggesting we cut out the middleman. By the way, another term for "constant buffer" is "uniform buffer", on the off chance it helps. Basically it's super-cached by the shader for values that never change across shader invocations...

...t's 0.) You don't even have to load these, you can use them as args >>>> directly anywhere you like (except as indirect addresses). >>>> >>>> The old code would actually take the supplied inputs, stick them into >>>> a constbuf, and then lower RINPUT accesses to load from that constbuf. >>>> I'm suggesting we cut out the middleman. >>>> >>>> By the way, another term for "constant buffer" is "uniform buffer", on >>>> the off chance it helps. Basically it's super-cached b...

...don't even have to load these, you can use them as > >> args > >> directly anywhere you like (except as indirect addresses). > >> > >> The old code would actually take the supplied inputs, stick them > >> into > >> a constbuf, and then lower RINPUT accesses to load from that > >> constbuf. > >> I'm suggesting we cut out the middleman. > >> > >> By the way, another term for "constant buffer" is "uniform > >> buffer", on > >> the off chance it helps. Basically it'...

...n >>> it's 0.) You don't even have to load these, you can use them as args >>> directly anywhere you like (except as indirect addresses). >>> >>> The old code would actually take the supplied inputs, stick them into >>> a constbuf, and then lower RINPUT accesses to load from that constbuf. >>> I'm suggesting we cut out the middleman. >>> >>> By the way, another term for "constant buffer" is "uniform buffer", on >>> the off chance it helps. Basically it's super-cached by the shader for...

...D TEMP[0].xy, TEMP[0].xyxy, TEMP[0].zwzw\n" " UADD TEMP[0].x, TEMP[0].xxxx, TEMP[0].yyyy\n" " UMUL TEMP[0].x, TEMP[0], IMM[0]\n" - " STORE RES[0].xyzw, TEMP[0], SV[0]\n" + " LOAD TEMP[1].x, RINPUT, IMM[2]\n" + " UADD TEMP[0].x, TEMP[0], TEMP[1]\n" + " STORE RGLOBAL.xyzw, TEMP[0], SV[0]\n" " UADD TEMP[0].x, TEMP[0], IMM[1]\n" - " STORE RES[0].xyzw, TEMP[0], SV[1]\n" +...