Hi all, While testing my own AA, I found it being queried for values that didn't exist previously. Luckily there's a pass built into LLVM for catching such things, "Debug-AA", and I used that to confirm that GVN does this fairly frequently. I've attached a test case that triggers the bug (reduced from Stanford/Treesort, for whatever that's worth), this is on LLVM 2.7. Should this be filed as a bug....? Additionally it just seems.. /unfortunate/ that we have a pass specifically designed to catch bugs like this, yet it's not being used. Don't suppose this is something someone would feel motivated to add this to some LLVM testing code? :) Thanks for your time, ~Will -------------- next part -------------- A non-text attachment was scrubbed... Name: DebugAA-GVN.ll Type: application/octet-stream Size: 3022 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100708/2db261fa/attachment.obj>
Filed bug report, sorry for the noise. ~Will On Thu, Jul 8, 2010 at 1:09 PM, Will Dietz <willdtz at gmail.com> wrote:> Hi all, > > While testing my own AA, I found it being queried for values that > didn't exist previously. Luckily there's a pass built into LLVM for > catching such things, "Debug-AA", and I used that to confirm that GVN > does this fairly frequently. > > I've attached a test case that triggers the bug (reduced from > Stanford/Treesort, for whatever that's worth), this is on LLVM 2.7. > > Should this be filed as a bug....? > > Additionally it just seems.. /unfortunate/ that we have a pass > specifically designed to catch bugs like this, yet it's not being > used. Don't suppose this is something someone would feel motivated to > add this to some LLVM testing code? :) > > Thanks for your time, > > ~Will >
Possibly Parallel Threads
- [LLVMdev] Request for Git Mirror of VMKit Subproject
- [LLVMdev] Request for Git Mirror of VMKit Subproject
- [LLVMdev] VMKit build error
- [LLVMdev] AliasAnalysis as a Loadable Module, Possible 2.6->2.7 issue
- [LLVMdev] AliasAnalysis as a Loadable Module, Possible 2.6->2.7 issue