search for: fnon

...platforms actually call the helper function). On other platforms, we don't generate explicit checks but instead let them signal, and then we have special code in the runtime to turn a signal into an exception. The second part here is that GCC knows about implicitly trapping instructions (the -fnon-call-exceptions flag, which we pass to all compilations for these targets). Tom

On Apr 23, 2006, at 9:32 PM, Archie Cobbs wrote: > Chris Lattner wrote: >>> I think the point of llvm-java was to avoid a JVM. That is, it >>> converts >> llvm-java is the JVM. >>> either Java source or Java bytecode into equivalent LLVM bytecode. I >> llvm-java only supports input from Java bytecode. >>> think the big thing lacking so far are

...elper > function). > > On other platforms, we don't generate explicit checks but instead let > them signal, and then we have special code in the runtime to turn a > signal into an exception. The second part here is that GCC knows > about implicitly trapping instructions (the -fnon-call-exceptions > flag, which we pass to all compilations for these targets). Ok, this makes sense. But I was actually asking how you deal with this in the LLVM JIT for libgcj (I guess it is too early for you to have an answer). Specifically, I don't think either of these approaches w...

> This is actually really easy to do, the big issue is defining the > 'bits' that we want to carry on each operation. For example, I think > it would be reasonable to have an "assume finite" bit (saying no > nan's / inf), it would also be useful to know you can do reassociation > etc, useful to know that you don't care about signed zero, etc. I think the

On Jan 14, 2010, at 2:01 AM, Duncan Sands wrote: > Hi Bill, > >> The current implementation of the "allow unsafe math" option is to >> specify it via the TargetOptions object. However, this prevents the >> target-independent optimizer from using it. Are there any opinions >> (ha!) on how this could be achieved in a nice clean manner which >>

Hi Chris, I've CC'd Eric Botcazou in the hope that he will clear up just what the Ada front-end needs from the rest of the compiler as far as asynchronous exceptions are concerned. >> gcc Ada turns signals into exceptions. As far as I know it does this >> completely asynchronously, and the fact that LLVM doesn't support this >> is rather bad as far as Ada is