[llvm] [Hexagon] Shrink __builtin_trap lowering from two words to one (PR #189210)

[Alexey Karyakin via llvm-commits]

quic-akaryaki wrote:

My concern is potential user confusion when they see an unfamiliar exception. I understand there will no message or even a self-explaining backtrace, just an invalid opcode exception right from the middle of the program. 
The current behavior is not better but at least user may have encountered 0xBADC0FEE. 
How do other platforms handle this? Is it typical to issue an opaque exception without a minimal diagnostics?

https://github.com/llvm/llvm-project/pull/189210