search for: imagesize

...the memory protections changed... No dice. A call to VirtualProtectEx then fails after adding it in... Any ideas on why this won't work in Wine? Here is some code where I added a lot of extra output for debugging... Code: static void doFork( EXE_FILE *exe, LPVOID ptrLoc, DWORD imageSize, char *target) { PROCESS_INFORMATION pi; CONTEXT ctx; PROCINFO childInfo; if (createChild(&pi, &ctx, &childInfo, target)) { LPVOID v = (LPVOID)NULL; DWORD r, old_protection = 0; MEMORY_BASIC_INFORMATION basic_info; printf("Origi...

...= s->cpp, - .pitch = width * s->cpp, + .pitch = pitch, }; offset += size; @@ -458,8 +494,10 @@ nouveau_teximage(struct gl_context *ctx, GLint dims, struct gl_texture_image *ti, GLint internalFormat, GLint width, GLint height, GLint depth, GLint border, + GLsizei imageSize, GLenum format, GLenum type, const GLvoid *pixels, - const struct gl_pixelstore_attrib *packing) + const struct gl_pixelstore_attrib *packing, + GLboolean compressed) { struct gl_texture_object *t = ti->TexObject; const GLuint level = ti->Level; @@ -472,9 +510,16 @@ nouveau_tex...

More questions on the best way to write a compiler using LLVM: Lets say I have a struct definition that looks like this: const int imageSize = 77; struct A { char B[align(imageSize)]; } ...where 'imageSize' is some small inline function that rounds up to a power of two or something. (A common requirement for textures on 3d graphics cards.) Now, clearly the compiler needs to evaluate the array size expression at co...

How to find out image width and height which is saved in database, with out using any applications or addons Please help --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe

.../* copy rows of blocks */ + for (i = 0; i < store.CopyRowsPerSlice; i++) { + memcpy(dst, src, store.CopyBytesPerRow); + dst += row_stride; + src += store.TotalBytesPerRow; + } +} + +static void nouveau_teximage(struct gl_context *ctx, GLint dims, struct gl_texture_image *ti, GLsizei imageSize, @@ -451,13 +476,19 @@ nouveau_teximage(struct gl_context *ctx, GLint dims, GL_MAP_WRITE_BIT, &map, &row_stride); - ret = _mesa_texstore(ctx, dims, ti->_BaseFormat, - ti->TexFormat, - row_stride, - &map, - ti->Width, ti->Hei...

...t; + dst += row_stride; >> + src += store.TotalBytesPerRow; >> + } >> +} >> + >> +static void >> nouveau_teximage(struct gl_context *ctx, GLint dims, >> struct gl_texture_image *ti, >> GLsizei imageSize, >> @@ -451,13 +476,19 @@ nouveau_teximage(struct gl_context *ctx, GLint dims, >> GL_MAP_WRITE_BIT, >> &map, &row_stride); >> >> - ret = _mesa_texstore(ctx, dims, ti-&gt...

...tem) == get_root_item() && !get_prev_sibling(item) </span><span class="cx"> end </span><span class="cx"> </span><del>- # TEMPORARILY DISABLED - def set_item_image(*args) - end </del><ins>+ def create_image_list + @imageSize = 16 </ins><span class="cx"> </span><del>- # TEMPORARILY DISABLED - def create_image_list(size = 16) - return false - if size == -1 - set_image_list(nil) - return nil - end - if size == 0 - size = @imageSize - else - @imageSize...

Hello, i am creating my XEN VM with virt-install (see below). When I create new images i do first an "df -h" to see if there is still enough space left on the drive. Are the XEN images pre allocated or does XEN only use that space that really is used by the VM inside the image? I know have the Problem that an "du -h" inside my /VM folder gives me nearly a higher number that

...ore.CopyRowsPerSlice; i++) { > + memcpy(dst, src, store.CopyBytesPerRow); > + dst += row_stride; > + src += store.TotalBytesPerRow; > + } > +} > + > +static void > nouveau_teximage(struct gl_context *ctx, GLint dims, > struct gl_texture_image *ti, > GLsizei imageSize, > @@ -451,13 +476,19 @@ nouveau_teximage(struct gl_context *ctx, GLint dims, > GL_MAP_WRITE_BIT, > &map, &row_stride); > > - ret = _mesa_texstore(ctx, dims, ti->_BaseFormat, > - ti->TexFormat, > - row_stride, > - &amp...

Hello all, I recently foudn myself wanting to view the basic blocks in the selection DAG as pure DAGs - so just as a list of edges, with no other information. I added the below code to the start of the " void SelectionDAGISel::CodeGenAndEmitDAG()" function. It creates a separate txt file for each basic block and gives a list of edges between nodes. The segment of code is below -

http://bugs.freedesktop.org/show_bug.cgi?id=23505 Summary: KDE's Kubrick has problems with xf86-video-nouveau driver Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at

...-05 23:19:57 UTC (rev 831) +++ trunk/wxruby2/samples/treectrl/treectrl.rb&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp2007-01-05 23:22:38 UTC (rev 832) </span><span class="lines">@@ -138,7 +138,7 @@ </span><span class="cx"> @imageSize = 16 </span><span class="cx"> </span><span class="cx"> # Make an image list containing small icons </span><del>- images = Wx::ImageList.new(16, 16, true) </del><ins>+ images = Wx::ImageList.new(32, 32, true) </ins>...

https://bugs.freedesktop.org/show_bug.cgi?id=27603 Summary: [nouveau] Celestia 1.6.0 crashes with nv04_surface_copy_swizzle assertion Product: Mesa Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=99396 Bug ID: 99396 Summary: Crash in nouveau_dri.so when switching apps with alt-tab in Gnome Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau