search for: glbl

...ct" and that should be a target specific node, as I don't think all .o formats can actually implement that. One other request that isn't in the PR, I'd like whatever replaces GEP to not store "i32 0" vs. "i64 0". Right now "i8* getelementptr ([1 x i8]* @glbl), i32 0, i32 0" is different from "i8* getelement ([1 x i8]* @glbl), i33 0, i33 0", and there's an infinite number of these. We should canonicalize these harder and only produce one Value* here. Nick > > Bug 10368 [1] tells me that ConstantExpr shouldn't automatical...

Hi all, It's been a long time, and I'm probably going to kill myself, but I want to try it anyway. Bug 10368 [1] tells me that ConstantExpr shouldn't automatically fold, and that this is source of many problems (most notably with traps) and code duplication. However, I'm a bit lost... There seem to be constant folding in many places like ConstantExpr::get*() uses

...be needed to run the other three packages in the dse bundle, but to be the only R package that deliberately does not work on one of the major platforms. I doubt if it works on Macs, either. It should not be in the main section of CRAN unless it does what it claims. > example(global.assign) glbl.s> date.parsed() Error in eval.with.vis(expr, envir, enclos) : couldn't find function "date.parsed" It has not been implemented! > example(system.call) systm.> system.call("ls") Error in system.call("ls") : system calls must be implemented for...