search for: clob

...] + +#define MOV_FROM_IPSR(pred, reg) \ +(pred) movl reg = XSI_IPSR; \ + ;; \ +(pred) ld8 reg = [reg] + +#define MOV_FROM_IIM(reg) \ + movl reg = XSI_IIM; \ + ;; \ + ld8 reg = [reg] + +#define MOV_FROM_IIP(reg) \ + movl reg = XSI_IIP; \ + ;; \ + ld8 reg = [reg] + +.macro __MOV_FROM_IVR reg, clob + .ifc "\reg", "r8" + XEN_HYPER_GET_IVR + .exitm + .endif + .ifc "\clob", "r8" + XEN_HYPER_GET_IVR + ;; + mov \reg = r8 + .exitm + .endif + + mov \clob = r8 + ;; + XEN_HYPER_GET_IVR + ;; + mov \reg = r8 + ;; + mov r8 = \clob +.endm +#define MOV_FROM_IVR...

...+/* check whether reg is a regular register */ +.macro is_rreg_in reg + .ifc "\reg", "r0" + nop 0 + .exitm + .endif + ;; + mov \reg = r0 + ;; +.endm +#define IS_RREG_IN(reg) is_rreg_in reg ; + +#define IS_RREG_OUT(reg) \ + ;; \ + mov reg = r0 \ + ;; + +#define IS_RREG_CLOB(reg) IS_RREG_OUT(reg) + +/* check whether pred is a predicate register */ +#define IS_PRED_IN(pred) \ + ;; \ + (pred) nop 0 \ + ;; + +#define IS_PRED_OUT(pred) \ + ;; \ + cmp.eq pred, p0 = r0, r0 \ + ;; + +#define IS_PRED_CLOB(pred) IS_PRED_OUT(pred) + + +#define DO_SAVE_MIN(__COVER...

...+/* check whether reg is a regular register */ +.macro is_rreg_in reg + .ifc "\reg", "r0" + nop 0 + .exitm + .endif + ;; + mov \reg = r0 + ;; +.endm +#define IS_RREG_IN(reg) is_rreg_in reg ; + +#define IS_RREG_OUT(reg) \ + ;; \ + mov reg = r0 \ + ;; + +#define IS_RREG_CLOB(reg) IS_RREG_OUT(reg) + +/* check whether pred is a predicate register */ +#define IS_PRED_IN(pred) \ + ;; \ + (pred) nop 0 \ + ;; + +#define IS_PRED_OUT(pred) \ + ;; \ + cmp.eq pred, p0 = r0, r0 \ + ;; + +#define IS_PRED_CLOB(pred) IS_PRED_OUT(pred) + + +#define DO_SAVE_MIN(__COVER...

We recently switched to Rails 1.1.2, which includes the latest version of ActiveRecord. This version seems to have introduced an error with the handling of non-binary large objects. The OCI adapter in 1.13.2 seemed to have treated CLOB and BLOB identically. The new Oracle adapter distinguishes between the two types and gives CLOB a type of :text, where as BLOB are :binary When it comes to insert or updating, only the binary fields are handled in the way that large objects should be handled (an after save callback). It is t...

...) PARENT_ID NUMBER ISM_PARENT_ID NUMBER REF_ID NUMBER MECHANISM_ID NUMBER ISM CLOB NORM_ISM CLOB COORDS CLOB CFLAG NUMBER VIS CLOB VAL CLOB...

Hi everyone, I have been following these forums closely for the last few months but this is my first time posting. Basically I am trying to get an Oracle SQL Developer Binary Large Object(BLOB/CLOB) file in as an R object in R. For those not familiar with a BLOB/CLOB file, it is basically lik a table that has cells that contain tables or files. By converting the large table into a BLOB/CLOB file the size of the file can be greatly reduced and processing for various applications improved. I a...

I have a field that is a clob within an Oracle database on Rails 0.13. Things have been working well until I tried to submit the field empty via a rails app at which point the following error was returned: ORA-24801: illegal parameter value in OCI lob function /app/controllers/publications_controller.rb:64:in `update''...

> It doesn't look like TableGen supports Constraints beyond EARLY_CLOBBER > and TIED_TO. We would need to add a constraint such as "$dst != $src1, > $dst != $mask, $src1 != $mask" to the current patterns to enforce the > rules. You can emulate such constraints via early clobbing. Just mark dst as early clobbing. > Is there another mechanism to...

...to the AVX2 manual, no two of the destination register, vector index register and mask register can be the same. The patterns in X86InstrSSE.td are missing this constraint and it's possible to generate an illegal instruction. It doesn't look like TableGen supports Constraints beyond EARLY_CLOBBER and TIED_TO. We would need to add a constraint such as "$dst != $src1, $dst != $mask, $src1 != $mask" to the current patterns to enforce the rules. Is there another mechanism to suport a constraint like this or is hacking TableGen the best way to do it? If the latter, does anyone ha...

Hello, I have been searching for it but could not find anything on Oracle different servers. Maybe someone here will be able to answer this question : Are CLOB and SYS.XML data type supported by OCFS? We need to migrate a 9.2.0.4 Windows Database having these data types to a 9.2.0.4 Linux Real Application Cluster with OCFS. This could cause an issue. Thanks in advance Philippe -------------- next part -------------- An HTML attachment was scrubbed.....

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. Changes from take 5 are rebased to Linux 2.6.26-rc3, bug fix ivt.S paravirtualization and multi entry point support. I believe these patches can be applied to the linux ia64 repository. This patchset does the followings. - Some preparation work. Mainly importing header files to

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. Changes from take 5 are rebased to Linux 2.6.26-rc3, bug fix ivt.S paravirtualization and multi entry point support. I believe these patches can be applied to the linux ia64 repository. This patchset does the followings. - Some preparation work. Mainly importing header files to

I''ve got a bunch of fairly large values (30kb each) I''m trying to insert into a CLOB column in my Oracle(10g) model. Since Rails is trying to create a typical insert statement with the entire value, this is causing a problem. Is there a trick I need to know to make this work, or am I out of luck? Thanks! -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------...

>> It doesn't look like TableGen supports Constraints beyond EARLY_CLOBBER >> and TIED_TO. We would need to add a constraint such as "$dst != $src1, >> $dst != $mask, $src1 != $mask" to the current patterns to enforce the >> rules. > You can emulate such constraints via early clobbing. Just mark dst as > early clobbing. How would tha...

This patchset is ia64/xen domU patch take 11. Tony, please commit those patches. They are ready to commit because all the issues which were pointed out had been addressed and got enough reviews. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate

This patchset is ia64/xen domU patch take 11. Tony, please commit those patches. They are ready to commit because all the issues which were pointed out had been addressed and got enough reviews. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate

This patchset is ia64/xen domU patch take 12. Tony, please commit those patches. They are ready to commit because all the issues which were pointed out had been addressed and got enough reviews. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate

This patchset is ia64/xen domU patch take 12. Tony, please commit those patches. They are ready to commit because all the issues which were pointed out had been addressed and got enough reviews. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate

...is how to generate code and its ABI. i.e. in-place generating v.s. direct jump v.s. indirect function call Indirect function call doesn't make sense because ivt.S is compiled multi times. And it is up to pv instances to choose in-place generating or direct jump. So what we should define is its clobbered registers. The ABI which this patch adopted is xen biased. Presumably we want to twist those macros to make more hypervisor neutral. (i.e. add more clobbered registers) Please comment. TODO: - more clean ups some macro needs clean up to be aware register usage r8, r9. - Free xen_ivt ares s...

...is how to generate code and its ABI. i.e. in-place generating v.s. direct jump v.s. indirect function call Indirect function call doesn't make sense because ivt.S is compiled multi times. And it is up to pv instances to choose in-place generating or direct jump. So what we should define is its clobbered registers. The ABI which this patch adopted is xen biased. Presumably we want to twist those macros to make more hypervisor neutral. (i.e. add more clobbered registers) Please comment. TODO: - more clean ups some macro needs clean up to be aware register usage r8, r9. - Free xen_ivt ares s...