Lines Matching full:lsda
56 // The action table follows the call-site table in the LSDA. The individual in computeActionsTable()
192 // try-ranges for them need be deduced so we can put them in the LSDA. in computePadMap()
227 // Later, one LSDA header will be emitted for each call-site range with its
439 // typeinfo objects at the end of the LSDA. However, unless we're in static in emitExceptionTable()
445 // from the LSDA, because the static linker will resolve it. in emitExceptionTable()
447 // 2) Otherwise, if the LSDA section is writable, we can output the direct in emitExceptionTable()
474 // Emit the LSDA. in emitExceptionTable()
491 // * For SJLJ and Wasm, they will be emitted only once in the LSDA header. in emitExceptionTable()
518 // In this case, we would need to calculate the LSDA size and the call in emitExceptionTable()
574 // when the data we use to represent the LSDA Size "needs" to be 1 byte in emitExceptionTable()
591 // emit the LSDA header. in emitExceptionTable()
621 // Itanium LSDA exception handling in emitExceptionTable()
625 // fragment. It immediately follows the LSDA header. Each entry indicates, in emitExceptionTable()
676 // Emit the LSDA header. in emitExceptionTable()