search for: clobbing

define xen paravirtualized instructions for hand written assembly code. Signed-off-by: Yaozu (Eddie) Dong <eddie.dong at intel.com> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: Akio Takebe <takebe_akio at jp.fujitsu.com> --- include/asm-ia64/xen/inst.h | 447 +++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 447 insertions(+), 0 deletions(-) create

This patch implements a checker to detect instructions which should be paravirtualized instead of direct writing raw instruction. This patch does rough check so that it doesn't fully cover all cases, but it can detects most cases of paravirtualization breakage of hand written assembly codes. Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: "Luck, Tony"

This patch implements a checker to detect instructions which should be paravirtualized instead of direct writing raw instruction. This patch does rough check so that it doesn't fully cover all cases, but it can detects most cases of paravirtualization breakage of hand written assembly codes. Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: "Luck, Tony"

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

Has anyone encountered this error or know how to correct it? I couldn''t find any Rails-specific info about this on google. Here are the circumstances: /usr/local/bin/ruby --version ruby 1.8.4 (2005-12-24) [i686-linux] /usr/local/bin/rails --version Rails 1.1.6 ## Create mcd app rails mcd -d oracle cd mcd ## Create oracle tablespace & user sqlplus ''/ as

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

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'' The line in question was: if

> 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 suport a constraint like this or is > hacking TableGen the best way to do it? If the latter, does anyone have > a sense of how difficult this would be to implement? It's not a tablegen problem, the regalloc part is the...

We've discovered a problem in the AVX2 gather patterns X86InstrSSE.td. According 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

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

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/.

...39;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 that (or any early clobbering) enforce $src1 != $mask? Or is it a fortuitous side-effect of implementation? Tim.

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

Hi. I rewrote the patch according to the comments. I adopted generating in-place code because it looks the quickest way. The point Eddie wanted to discuss 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

Hi. I rewrote the patch according to the comments. I adopted generating in-place code because it looks the quickest way. The point Eddie wanted to discuss 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