The problem is happening when user passes lambda function with reference
type in the map clause.
The natural of the problem is when processing generateInfoForCapture, the
BasePointer is generated with new load for a lambda variable with reference
type. It is not expected in adjustMemberOfForLambdaCaptures.
One way to fix this is to skipping call to generateInfoForCapture for
map(to:lambda). The map info will be generated later in the call to
generateDefaultMapInfo, samiler as firsprivate clase.
This to fix https://bugs.llvm.org/show_bug.cgi?id=52071
No need to create empty ArrayRefs, just pass llvm::None instead.