bugzilladebuginfogood first issuemetaissue
Description
| Bugzilla Link | 37953 |
| Version | trunk |
| OS | All |
| Depends On | llvm/llvm-project#37089 llvm/llvm-project#37303 llvm/llvm-project#37362 llvm/llvm-project#37290 llvm/llvm-project#37302 llvm/llvm-project#37304 llvm/llvm-project#37307 llvm/llvm-project#37308 llvm/llvm-project#37309 llvm/llvm-project#37310 llvm/llvm-project#37312 llvm/llvm-project#37314 llvm/llvm-project#37315 llvm/llvm-project#37371 llvm/llvm-project#37430 llvm/llvm-project#37431 llvm/llvm-project#37510 llvm/llvm-project#37511 llvm/llvm-project#37525 llvm/llvm-project#37526 llvm/llvm-project#37527 |
| CC | @adrian-prantl,@dwblaikie,@emaste,@flametop,@jmorse,@jdm,@jryans,@mikaelholmen,@pogo59,@Trass3r,@vedantk,@wjristow,@yurybura |
Extended Description
This is a meta bug for tracking work related to fixing all known failures from debugify ( https://reviews.llvm.org/D40512 ).
The motivation for this is in order to provide the best possible user experience when debugging optimized code by ensuring that optimization passes preserve debug information wherever possible.
From Bug 37942, Comment 1:
An error report from -check-debugify should always be considered a compiler bug. It would be cumbersome if we couldn't rely on this -- so much so that we should consider relaxing -check-debugify rather than allowing it to emit false positives.