search for: get_tokens

...tions=t.PARSE_DETAILED_PROCESSING_RECORD | t.PARSE_PRECOMPILED_PREAMBLE src1 =""" #define TEST 5 """ tu = t.from_source('t.c',"",unsaved_files=[('t.c',src1)],options=options) cursor = get_cursor(tu.cursor,'TEST') tokens = list(cursor.get_tokens()) print tokens[-1].spelling #Prints 5 OK src2 = """ #define TEST 5 typedef int int8; """ tu = t.from_source('t.c',"",unsaved_files=[('t.c',src2)],options=options) cursor = get_cursor(tu.cursor,'TEST') tokens = list(cursor.get_tokens(...

Hi, i started using oauth2 gem by intridea (http://github.com/intridea/oauth2) and don''t know how to fix this problem. I have developed both client and server and on request for access_token i see no grant_type parameter. My code from client callback controller class CallbackController < Devise::OauthCallbacksController def accounts access_token =

Hi, Here are patches which implement the support for OpenCL kernel input parameters we discussed. They also add the tgsi parsing bits for adding support for global / local mem, but no implementation yet. Regards, Hans

...eturn reg; > } > > @@ -1666,7 +1667,7 @@ emit_decl_buffer(struct ureg_program *ureg, > } > > static void > -emit_decl_shared_memory(struct ureg_program *ureg) > +emit_decl_memory(struct ureg_program *ureg, unsigned memory_type) > { > union tgsi_any_token *out = get_tokens(ureg, DOMAIN_DECL, 2); > > @@ -1675,11 +1676,11 @@ emit_decl_shared_memory(struct ureg_program *ureg) > out[0].decl.NrTokens = 2; > out[0].decl.File = TGSI_FILE_MEMORY; > out[0].decl.UsageMask = TGSI_WRITEMASK_XYZW; > - out[0].decl.Shared = true; > + out[0].decl...

When support for decl.Atomic and .Shared was added, tgsi_build_declaration was not updated to propagate these properly. Signed-off-by: Hans de Goede <hdegoede at redhat.com> Reviewed-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Changes in v2: -Add Reviewed-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/gallium/auxiliary/tgsi/tgsi_build.c | 6 ++++++ 1 file changed, 6

...ureg->use_memory[memory_type] = true; return reg; } @@ -1666,7 +1667,7 @@ emit_decl_buffer(struct ureg_program *ureg, } static void -emit_decl_shared_memory(struct ureg_program *ureg) +emit_decl_memory(struct ureg_program *ureg, unsigned memory_type) { union tgsi_any_token *out = get_tokens(ureg, DOMAIN_DECL, 2); @@ -1675,11 +1676,11 @@ emit_decl_shared_memory(struct ureg_program *ureg) out[0].decl.NrTokens = 2; out[0].decl.File = TGSI_FILE_MEMORY; out[0].decl.UsageMask = TGSI_WRITEMASK_XYZW; - out[0].decl.Shared = true; + out[0].decl.MemType = memory_type; out...

...ureg->use_memory[memory_type] = true; return reg; } @@ -1672,7 +1673,7 @@ emit_decl_buffer(struct ureg_program *ureg, } static void -emit_decl_shared_memory(struct ureg_program *ureg) +emit_decl_memory(struct ureg_program *ureg, unsigned memory_type) { union tgsi_any_token *out = get_tokens(ureg, DOMAIN_DECL, 2); @@ -1681,11 +1682,11 @@ emit_decl_shared_memory(struct ureg_program *ureg) out[0].decl.NrTokens = 2; out[0].decl.File = TGSI_FILE_MEMORY; out[0].decl.UsageMask = TGSI_WRITEMASK_XYZW; - out[0].decl.Shared = true; + out[0].decl.MemType = memory_type; out...

Hi everyone, These patchsets are the new releases of dm-ioband and bio-cgroup which are ported to 2.6.27-rc5-mm1. dm-ioband Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same block device. A job is a group of processes with the same pid or pgrp or uid or a virtual machine such as KVM or Xen. A

Hi everyone, These patchsets are the new releases of dm-ioband and bio-cgroup which are ported to 2.6.27-rc5-mm1. dm-ioband Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same block device. A job is a group of processes with the same pid or pgrp or uid or a virtual machine such as KVM or Xen. A

Hi everyone, These patchsets are the new releases of dm-ioband and bio-cgroup which are ported to 2.6.27-rc5-mm1. dm-ioband Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same block device. A job is a group of processes with the same pid or pgrp or uid or a virtual machine such as KVM or Xen. A

Hi everyone, This is the dm-ioband version 1.3.0 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. - Can be applied to the kernel 2.6.26-rc5-mm3. - Changes from 1.2.0 (posted on Jul 4, 2008): - I/O smoothing take #2 This feature makes I/O requests of each group issued

Hi everyone, This is the dm-ioband version 1.3.0 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. - Can be applied to the kernel 2.6.26-rc5-mm3. - Changes from 1.2.0 (posted on Jul 4, 2008): - I/O smoothing take #2 This feature makes I/O requests of each group issued

Hi everyone, This is the dm-ioband version 1.3.0 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. - Can be applied to the kernel 2.6.26-rc5-mm3. - Changes from 1.2.0 (posted on Jul 4, 2008): - I/O smoothing take #2 This feature makes I/O requests of each group issued

Hi everyone, This is the dm-ioband version 1.7.0 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. - Can be applied to the kernel 2.6.27-rc5-mm1. - Changes from 1.6.0 (posted on Sep 24, 2008): - Fix a problem that processes issuing I/Os are permanently blocked when I/O

Hi everyone, This is the dm-ioband version 1.7.0 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. - Can be applied to the kernel 2.6.27-rc5-mm1. - Changes from 1.6.0 (posted on Sep 24, 2008): - Fix a problem that processes issuing I/Os are permanently blocked when I/O

Hi everyone, This is the dm-ioband version 1.7.0 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. - Can be applied to the kernel 2.6.27-rc5-mm1. - Changes from 1.6.0 (posted on Sep 24, 2008): - Fix a problem that processes issuing I/Os are permanently blocked when I/O

...-1666,7 +1667,7 @@ emit_decl_buffer(struct ureg_program *ureg, >> } >> >> static void >> -emit_decl_shared_memory(struct ureg_program *ureg) >> +emit_decl_memory(struct ureg_program *ureg, unsigned memory_type) >> { >> union tgsi_any_token *out = get_tokens(ureg, DOMAIN_DECL, 2); >> >> @@ -1675,11 +1676,11 @@ emit_decl_shared_memory(struct ureg_program *ureg) >> out[0].decl.NrTokens = 2; >> out[0].decl.File = TGSI_FILE_MEMORY; >> out[0].decl.UsageMask = TGSI_WRITEMASK_XYZW; >> - out[0].decl.Shared =...

Hi Alasdair and all, This is the dm-ioband version 1.8.0 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. This release is a minor bug fix and confirmed running on the latest stable kernel 2.6.27.1. - Can be applied to the kernel 2.6.27.1 and 2.6.27-rc5-mm1. - Changes from

Hi Alasdair and all, This is the dm-ioband version 1.8.0 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. This release is a minor bug fix and confirmed running on the latest stable kernel 2.6.27.1. - Can be applied to the kernel 2.6.27.1 and 2.6.27-rc5-mm1. - Changes from

Hi Alasdair and all, This is the dm-ioband version 1.8.0 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. This release is a minor bug fix and confirmed running on the latest stable kernel 2.6.27.1. - Can be applied to the kernel 2.6.27.1 and 2.6.27-rc5-mm1. - Changes from