search for: xchk

...% c("X11", "jpeg", "png", "tiff"))) { ## This might throw an X11 error z[nas] <- tryCatch(.Internal(capabilitiesX11()), error = function(e) FALSE) } z } and we could easily add a 2nd argument, say 'Xchk = TRUE' like this capabilities <- function(what = NULL, Xchk = TRUE) { z <- .Internal(capabilities()) if(!is.null(what)) z <- z[match(what, names(z), 0L)] if(.Platform$OS.type == "windows") return(z) if(Xchk) { ## Now we need to deal with any NA en...

>> I've built a pass to split critical edges of machine functions, and I have >> to insert new basic blocks. Some of them will have MBB->begin() == >> MBB->end(). > > Ah, machine basic blocks are different. They *are* allowed to be empty. > I would like to build an "insertNoOp" and add it to MRegisterInfo. I would have one for each target. For the

...have your code handle them. Currently, that is the solution. I have a special treatment for empty basic blocks. I think the code would be more homogeneous if there were no empty basic blocks. > > There is a NOP "instruction" on x86, equivalent to XCHG EAX, EAX. The problem with xchk EAX, EAX is that is uses registers, and it would add a small burden on the register allocator. Fernando

On Jul 13, 2007, at 10:53 AM, Fernando Magno Quintao Pereira wrote: > >>> I've built a pass to split critical edges of machine functions, >>> and I have >>> to insert new basic blocks. Some of them will have MBB->begin() == >>> MBB->end(). >> >> Ah, machine basic blocks are different. They *are* allowed to be >> empty.

Hello, Fernando. > The problem with xchk EAX, EAX is that is uses registers, and it would > add a small burden on the register allocator. There is "just" NOP instruction on x86. Its opcode is 0x90. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

...ests option is always specified. Thanks to Reinhold Koch for the suggestion. * New function R_user_dir() in package tools suggests paths appropriate for storing R-related user-specific data, configuration and cache files. * capabilities() gains a new logical option Xchk to avoid warnings about X11-related capabilities. * The internal implementation of grid units has changed, but the only visible effects at user-level should be * a slightly different print format for some units (especially unit arithmetic), * faster perf...

...ests option is always specified. Thanks to Reinhold Koch for the suggestion. * New function R_user_dir() in package tools suggests paths appropriate for storing R-related user-specific data, configuration and cache files. * capabilities() gains a new logical option Xchk to avoid warnings about X11-related capabilities. * The internal implementation of grid units has changed, but the only visible effects at user-level should be * a slightly different print format for some units (especially unit arithmetic), * faster perf...

...ests option is always specified. Thanks to Reinhold Koch for the suggestion. * New function R_user_dir() in package tools suggests paths appropriate for storing R-related user-specific data, configuration and cache files. * capabilities() gains a new logical option Xchk to avoid warnings about X11-related capabilities. * The internal implementation of grid units has changed, but the only visible effects at user-level should be * a slightly different print format for some units (especially unit arithmetic), * faster perf...