Displaying 5 results from an estimated 5 matches for "exceptionnal".
Did you mean:
exceptional
2008 May 10
0
[LLVMdev] How to handle divide-by-zero exception?
DISCLAIMER: I am SSA, LLVM and compiler ignorant, so take the following for
what it is worth.
What about logically breaking a (complex) SEH method into two logical
methods, as per this pseudo-code as an example:
-----------------------
foo(parameter-list)
{
leading-statements;
try {
try-statements;
}
catch(Execption0 ex0) {
catch-0-statements;
}
.
catch(ExceptionN exN) {
2017 Feb 20
0
NHW Project - some advice
Hello,
Ok that's right HEVC and AOM AV1 are better than the NHW codec, even at mid
compression.I only tested my codec with quite neat images, hence the good
results, but on more blurred, more compressed images, HEVC and AOM AV1 are
definitely better, they are also exceptionnal at high compression.
So, yes that's right, the NHW codec has very little chance to penetrate the
market, it is still royalty-free and a lot faster to compute, which _are_
good advantages and it can be still improved.
That said, it will be very difficult to find a company or an organization
th...
2008 May 10
1
[LLVMdev] How to handle divide-by-zero exception?
Hi,
> What about logically breaking a (complex) SEH method into two logical
> methods, as per this pseudo-code as an example:
>
> -----------------------
>
> foo(parameter-list)
> {
> leading-statements;
>
> try {
> try-statements;
> }
> catch(Execption0 ex0) {
> catch-0-statements;
> }
> .
> catch(ExceptionN exN) {
>
2008 May 09
4
[LLVMdev] How to handle divide-by-zero exception?
On May 8, 2008, at 9:35 PM, Nick Lewycky wrote:
> Talin wrote:
>> Currently it states in the language manual that the results of
>> division
>> by zero are undefined. However, I'm curious as to how you would
>> normally
>> handle either divide by zero or other "hardware" exceptions (null
>> pointer dereference and so on) and turn them into
2009 Sep 04
4
[LLVMdev] An alternate implementation of exceptions
Hi Duncan,
I agree on the problem about linking with code - I actually do mention
this in the paper. I propose adding a new calling convention called
"excall".
The central point of my paper is that only one parameter is needed as the
return value (because of the use of the flag): the EAX register can safely
be used for both the exception instance and the return value as these
never