search for: nowthat

...here... Help? Geoff On Mon, Aug 10, 2020 at 4:43 PM Johannes Doerfert <johannesdoerfert at gmail.com> wrote: > > This looks strange but it makes sense that you see the assertion > "because of" that patch. > > We use this code path to generate OpenMP code for a while nowthat is why > I am not convinced there is not another (undiagnosed) problem which is > the actual cause. > > Could you run it with `-debug-only='openmp-opt,openmp-ir-builder'` > please? Is it possible you merged in an old module or some user code > with OpenMP declarations? &gt...

...0 at 4:43 PM Johannes Doerfert > > <johannesdoerfert at gmail.com> wrote: > >> This looks strange but it makes sense that you see the assertion > >> "because of" that patch. > >> > >> We use this code path to generate OpenMP code for a while nowthat is why > >> I am not convinced there is not another (undiagnosed) problem which is > >> the actual cause. > >> > >> Could you run it with `-debug-only='openmp-opt,openmp-ir-builder'` > >> please? Is it possible you merged in an old module or some...

...hannes Doerfert >>> <johannesdoerfert at gmail.com> wrote: >>>> This looks strange but it makes sense that you see the assertion >>>> "because of" that patch. >>>> >>>> We use this code path to generate OpenMP code for a while nowthat is why >>>> I am not convinced there is not another (undiagnosed) problem which is >>>> the actual cause. >>>> >>>> Could you run it with `-debug-only='openmp-opt,openmp-ir-builder'` >>>> please? Is it possible you merged in an old...

Hi, That patch was from an ongoing effort to consolidate OpenMP generation in clang. If memory serves the implementation there is still a little incomplete. It's supposed to use types from OMPConstants rather than ones it defined itself and the methods used to create the functions shouldn't need to be static. However attempting this caused a lot of errors so there might be an underlying