Displaying 3 results from an estimated 3 matches for "dagselect".
Did you mean:
lagselect
2013 Jul 09
1
[LLVMdev] Optimization issue for target's offset field of load operation in DAGSelection
...am working on an experimental target and trying to make sure that
the load offset field is used to the best way. There appears to be
some control over the architecture's offset range and whether the
offset is too large and needs to be lowered/converted into a separate
sequence of operations in DAGSelection?
Can someone point me to what might be the case?
For example, the difference between index=63 and 64 causes the
difference in address+offset being generated as separate operation
versus built into the architecture versus just a load operation. In my
architecture, there are larger offsets and 6...
2007 Mar 28
2
[LLVMdev] llvm-gcc4_2
...e testsuite will not be the
> > criteria.
>
> Hrm, that's strange. llvm-test doesn't pass 100% (e.g. some of the EH
> stuff is now working yet), but it should ahve basic functionality. What
> is broken?
>
major error causes:
the sse.* tests produce errors during dagselection (see log)
there is a problem when exception handling is used because
all the __cxa.* functions are not found (bei llc and when compiling c-backend code) (i guess thats what you were refering to)
and a few other failures i did not relate to this 2 groups
for more information:
here is a list...
2007 Mar 30
0
[LLVMdev] llvm-gcc4_2
...look quite far along.
>> Hrm, that's strange. llvm-test doesn't pass 100% (e.g. some of the EH
>> stuff is now working yet), but it should ahve basic functionality. What
>> is broken?
>>
>
> major error causes:
>
> the sse.* tests produce errors during dagselection (see log)
>
> there is a problem when exception handling is used because
> all the __cxa.* functions are not found (bei llc and when compiling c-backend code) (i guess thats what you were refering to)
>
> and a few other failures i did not relate to this 2 groups
Right, C++ EH is...