Displaying 4 results from an estimated 4 matches for "logsch".
Did you mean:
loesch
2004 Apr 22
2
[LLVMdev] Motivation for 'select' instruction
...motivaton for the 'select' instruction.
Was it for convenience, or for some deep reason. I'm asking because it's
causing me some problems (see below) and I'd like to know I understand the
situation before working those problems around.
I have the following function:
int logsch(int ih,int nbh)
{
if(nbh < 0) { nbh = 0; ih = 10; }
if(nbh > 22528) { nbh = 22528; ih = 7; }
return(nbh + ih);
}
2004 Apr 22
0
[LLVMdev] Motivation for 'select' instruction
...to
unconditionally execute the body than it is to execute the branch. If
this is the case, we like to use the select when possible. Once the
control flow is turned into data flow, the optimizers are also able to do
good things eliminating it.
> I have the following function:
>
> int logsch(int ih,int nbh)
> {
> if(nbh < 0) { nbh = 0; ih = 10; }
> if(nbh > 22528) { nbh = 22528; ih = 7; }
> return(nbh + ih);
> }
>
> >From the C language standpoint, there are 4 paths though this function: each
> "if" can be ei...
2004 Apr 22
2
[LLVMdev] Motivation for 'select' instruction
...n
LLVM.
> > "if" can be either take or not. In reality, both "if" can't be taked at
> > the same time -- and that's why I'm trying to automatically figure out
> > working on LLVM representation. However, the LLVM code:
> >
> > int %logsch(int %ih, int %nbh) {
> > entry:
> > %tmp.1 = setlt int %nbh, 0
> > %ih_addr.1 = select bool %tmp.1, int 10, int %ih
> > %nbh_addr.1 = select bool %tmp.1, int 0, int %nbh
> > %tmp.4 = setgt int %nbh_addr.1, 22528
&...
2004 Apr 22
0
[LLVMdev] Motivation for 'select' instruction
On Thu, 22 Apr 2004, Vladimir Prus wrote:
> > > int %logsch(int %ih, int %nbh) {
> > > entry:
> > > %tmp.1 = setlt int %nbh, 0
> > > %ih_addr.1 = select bool %tmp.1, int 10, int %ih
> > > %nbh_addr.1 = select bool %tmp.1, int 0, int %nbh
> > > %tmp.4 = setgt...