search for: hexagoncommongep

Hi All, Skim through Hexagon backend, I notice there is HexagonCommonGEP.cpp which seems try to do something on `getelementptr` LLVM instruction. But what exactly it want to do? Anyone knows? Thanks. Regards, chenwj -- Wei-Ren Chen (陳韋任) Homepage: https://people.cs.nctu.edu.tw/~chenwj -------------- next part -------------- An HTML attachment was scrubbed... URL:...

...ingle getelementptr into a few smaller ones, then do CSE-like optimization? 2017-06-14 21:11 GMT+08:00 Krzysztof Parzyszek via llvm-dev < llvm-dev at lists.llvm.org>: > On 6/14/2017 7:44 AM, 陳韋任 via llvm-dev wrote: > >> >> Skim through Hexagon backend, I notice there is HexagonCommonGEP.cpp >> which seems >> try to do something on `getelementptr` LLVM instruction. But what exactly >> it want to do? >> Anyone knows? >> > > Each getelementptr is a chain that starts with a pointer, followed by an > index, which together produce a new pointer. Th...

I only see Hexagon has such optimization, is there any reason that Hexagon need this? No existing optimization does similar thing? Thanks, Regards, chenwj 2017-06-14 21:51 GMT+08:00 Krzysztof Parzyszek <kparzysz at codeaurora.org>: > On 6/14/2017 8:16 AM, 陳韋任 wrote: > >> Sounds like you break a single getelementptr into a few smaller ones, >> then do CSE-like

Krzystof, Is this partly due to hardware loops not being common? I'm curious, we do something very similar for similar reasons. On Wed, Jun 14, 2017 at 10:23 AM, Krzysztof Parzyszek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On 6/14/2017 9:05 AM, 陳韋任 wrote: > >> I only see Hexagon has such optimization, is there any reason that >> Hexagon need this?