search for: sub_sat

...add the operands, saturate the result before it's assigned to c */ > c = add_sat(-0.75, -0.75); The way it is expressed at the source language isn't important. However it is expressed there, it should be lowered to llvm operations that express what happens to the data (e.g. add_sat, sub_sat, etc). > 2. memory space qualifier > > a typical program will have its global variables and constant in > different data segments. a segment is just a block with continuous > memory. there is no difference where the segment is. however, it's > different in the embedded system...

fixed-point number could be stored in LLVM first class integer types. i cannot see the problem now. but to be type-safe, there should be a first class 'fixed'. some llvm extensions required to mapping dsp-c lanaguages could be implemented as qualifiers. 1. _sat qualifier Saturate the result within [0.0, +1.0> or [-1.0,+1.0> (unsigned/singed). sat signed fixed a; sat signed fixed

It's not clear what is actually wrong from your original message, I think you need to give some more information as to what you are doing: Example source, what target GPU, compiler error messages or other evidence of "it's wrong" (llvm IR, disassembly, etc) ... -- Mats On 8 April 2016 at 09:55, Liu Xin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I built it