search for: fenv

...===================== downloaded 78 KB installing source package 'markdown' ... ** package 'markdown' successfully unpacked and MD5 sums checked ** libs /opt/ibm/xlC/13.1.6/bin/xlc_r -q64 -I/usr/local/lib64/R/include -DNDEBUG -I/usr/local/include -qpic -g -O2 -qstrict -qfloat=nomaf:fenv -c Rbase64.c -o Rbase64.o /opt/ibm/xlC/13.1.6/bin/xlc_r -q64 -I/usr/local/lib64/R/include -DNDEBUG -I/usr/local/include -qpic -g -O2 -qstrict -qfloat=nomaf:fenv -c Rinit.c -o Rinit.o /opt/ibm/xlC/13.1.6/bin/xlc_r -q64 -I/usr/local/lib64/R/include -DNDEBUG -I/usr/local/include -qpic -g -O2 -qstrict...

...rs on code that worked as I intended previously. Briefly, I am using bquote to generate expressions to modify data.table objects within a function, so I need the changes to actually be stored in the given environment. Previously, I used code like the following: test <- list(bquote(x <- 10)) fenv <- environment() rapply(test, evalq, envir = fenv) Although the code in the example above is much simpler, it shows the problem. On 3.1.2 the expression is evaluated and x is stored as 10 in the given environment, fenv. In 3.2.1 the code throws an error: Error in eval(substitute(expr), envir,...

Howdy all, I've been playing around with programs that use the C11 fenv.h. It seems that, currently, the LLVM compiler does not regard to the exception-flag side-effects of floating point operations? When run on my macbook, the example code on http://en.cppreference.com/w/c/numeric/fenv/FE_exceptions does not print all the expected exceptions. Other examples: vo...

...t store the result of the bquote-generated call in the given environment. Interestingly, in 3.2.1 eval does store the result of the bquote-generated call in the given environment. In other words if I run the given example with eval rather than evalq, on 3.1.2 "x" is never stored in "fenv," but it is when I run the same code on 3.2.1. However, the given example stores "x" in "fenv" on 3.1.2, but throws the error I gave when run on 3.2.1. To give credit, I received the idea for using evalq from SO: http://stackoverflow.com/a/22559385 Dayne On Wed, Jul 15,...

David, If you are referring to the solution that would be: rapply(list(test), eval, envir = fenv) I thought I explained in the question that the above code does not work. It does not throw an error, but the behavior is no different (at least in the output or result). Using the above code still results in the x object not being stored in fenv on 3.1.2. Dayne On Wed, Jul 15, 2015 at 4:40 PM,...

...ll in >> the given environment. Interestingly, in 3.2.1 eval does store the result >> of the bquote-generated call in the given environment. >> >> In other words if I run the given example with eval rather than evalq, on >> 3.1.2 "x" is never stored in "fenv," but it is when I run the same code on >> 3.2.1. However, the given example stores "x" in "fenv" on 3.1.2, but throws >> the error I gave when run on 3.2.1. >> >> To give credit, I received the idea for using evalq from SO: >> http://stackove...

On Fri, Mar 08, 2013 at 12:33:58AM +0800, Jiong Wang wrote: > please review, thanks. configure.ac: I guess it would be preferable to not enable it by default for the moment. include/llvm/Support/FEnv.h: What is supposed to handle? Build on/for Tile? Does the platform provide fenv.h but in a broken way? lib/Target/Mips/MCTargetDesc/MipsMCAsmInfo.cpp: Is this change intentional? Personally, I would like to see this in the tree sooner than later :) Joerg

...your conclusion to just update the code and enforce using the most recent version of R? Dayne On Wed, Jul 15, 2015 at 4:44 PM, Dayne Filer <dayne.filer at gmail.com> wrote: > David, > > If you are referring to the solution that would be: > > rapply(list(test), eval, envir = fenv) > > I thought I explained in the question that the above code does not work. > It does not throw an error, but the behavior is no different (at least in > the output or result). Using the above code still results in the x object > not being stored in fenv on 3.1.2. > > Dayne &...

...e bquote-generated call in > the given environment. Interestingly, in 3.2.1 eval does store the result > of the bquote-generated call in the given environment. > > In other words if I run the given example with eval rather than evalq, on > 3.1.2 "x" is never stored in "fenv," but it is when I run the same code on > 3.2.1. However, the given example stores "x" in "fenv" on 3.1.2, but throws > the error I gave when run on 3.2.1. > > To give credit, I received the idea for using evalq from SO: > http://stackoverflow.com/a/22559385...

...vm.org> wrote: > I note that on your bug that you have stated that the branch is faster than > the conditional move. Faster code is a side effect of the fix in this > particular case. On the contrary: the faster code is pretty much the only reason this can happen before the rest of the FENV support lands. It's been said before, but I'll reiterate: LLVM IR does not model the FENV on its instructions. CodeGen and other passes are free to de-conditionalize exceptions, remove them, or add spurious ones just for the giggles. What LLVM does now is not incorrect. Tim.

...ronment. Interestingly, in 3.2.1 eval does store the > result > >> of the bquote-generated call in the given environment. > >> > >> In other words if I run the given example with eval rather than evalq, > on > >> 3.1.2 "x" is never stored in "fenv," but it is when I run the same code > on > >> 3.2.1. However, the given example stores "x" in "fenv" on 3.1.2, but > throws > >> the error I gave when run on 3.2.1. > >> > >> To give credit, I received the idea for using evalq from...

...ntended previously. Briefly, I am using bquote to generate > expressions to modify data.table objects within a function, so I need the > changes to actually be stored in the given environment. Previously, I used > code like the following: > > test <- list(bquote(x <- 10)) > fenv <- environment() > rapply(test, evalq, envir = fenv) > > Although the code in the example above is much simpler, it shows the > problem. On 3.1.2 the expression is evaluated and x is stored as 10 in the > given environment, fenv. In 3.2.1 the code throws an error: > > Error...

...groupMembers) { gpDef <- getGeneric(gp) if(is(gpDef, "genericFunction")) .getMethodsTable(gpDef) # force initialization w. group methods } } NULL } ############### .updateMethodsInTable <- function(generic, where, attach) { fenv <- environment(generic) reset <- identical(attach, "reset") if(!exists(".MTable", envir = fenv, inherits = FALSE)) .setupMethodsTables(generic) ### !!! mtable <- get(".MTable", envir = fenv) if(!reset) { env <- as.environment(wh...

Wait, back up, what? The invalid flag raised by operations on sNaN is no different from any other flag in fenv. There’s nothing sensible about saying that every operation that raises underflow/overflow/inexact is undefined, why are operations on sNaN any different? – Steve > On Feb 28, 2018, at 11:41 PM, Chris Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > However, fdiv/fmul/...

...> >From what I remember, this is a bug in debian libc: > some floating point flags are set incorrectly causing SIGFPE. > Can't find the bug report ATM. Oh, it just showed up on numpy-discussion: http://sources.redhat.com/bugzilla/show_bug.cgi?id=10 """ #include <fenv.h> void feclearexcept(int ex) This function should clear the specified exception status bits in the FPU status register. For CPUs with SSE support it should also clear the MXCSR status register bits. The problem is that feclearexcept() clears the status control bits also, causing future floati...

On Tue, 18 Apr 2006 23:27:39 -0700 Evan Cheng <evan.cheng at apple.com> wrote: > Hi Simon, > > The x86 backend does generate scalar SSE2 instructions. For your > example, it should emit something like: Oh, how did you get this ? [...] > > There is nothing here that should cause an exception. Are you using a > release or cvs? CVS. >From what I remember,

Hi all, Updated the patches for TILE-Gx backend: 1. added initial regression tests for tilegx codegen. 2. added initial regression tests for MC Layer. 3. fixed those commenting style issues. please review, thanks. I have tried to understand the new backend requirement for LLVM from the mailiing list archive, it's sure TILE-Gx backend will be actively maintained & improved, it's

Attached please find unified diffs against Samba 2.0.6. I'm hoping that others will find it useful and that it may even find its way into Samba 2.0.7 This patch does two things: - Modifies the handling of the 'netbios name' parameter so that standard_sub_basic() is run on its value when the 'netbios name' parameter is processed. This has to be done this way because

On 03/02/2013 04:50 AM, Dmitri Gribenko wrote: > You also need tests for Clang bits, too. > > Mechanical issues: > > +/// getTileRegisterNumbering - Given the enum value for some register, > +/// return the number that it corresponds to. > > Please don't duplicate function and class name in comments. Existing > code does this, but current style guidelines advise not

> > I'm not sure why this is an issue. Yes, these two intrinsics depend > on the current rounding mode according to the C standard, and yes, > LLVM in default mode assumes that the current rounding mode is the > default rounding mode. But the same holds true for many other > intrinsics and even the arithmetic IR operations like add. Any other intrinsic, like `floor`,