search for: toselectiondag

In the continuing quest to try to track down problems we're seeing in SelectionDAG, I added the following assert toSelectionDAG::ReplaceAllUsesOfValuesWith: // Read up all the uses and make records of them. This helps // processing new uses that are introduced during the // replacement process. SmallVector<UseMemo, 4> Uses; for (unsigned i = 0; i != Num; ++i) { unsigned FromResNo = From[i].getResNo();...

On Friday 26 February 2010 09:55:32 David Greene wrote: > In the continuing quest to try to track down problems we're seeing in > SelectionDAG, I added the following assert > toSelectionDAG::ReplaceAllUsesOfValuesWith: Here's a patch to add more of these deleted node asserts. They fire tons of times in the testbase. This concerns me greatly. Are all of these asserts valid? If not, we should document why with comments in the source....

On Friday 26 February 2010 10:34:41 David Greene wrote: > On Friday 26 February 2010 09:55:32 David Greene wrote: > > In the continuing quest to try to track down problems we're seeing in > > SelectionDAG, I added the following assert > > toSelectionDAG::ReplaceAllUsesOfValuesWith: > > Here's a patch to add more of these deleted node asserts. They fire > tons of times in the testbase. Ping? Just want to make sure this didn't get missed somehow. I'm surprised to see no discussion....

...: > On Friday 26 February 2010 10:34:41 David Greene wrote: >> On Friday 26 February 2010 09:55:32 David Greene wrote: >>> In the continuing quest to try to track down problems we're seeing >>> in >>> SelectionDAG, I added the following assert >>> toSelectionDAG::ReplaceAllUsesOfValuesWith: >> >> Here's a patch to add more of these deleted node asserts. They fire >> tons of times in the testbase. > > Ping? Just want to make sure this didn't get missed somehow. I'm > surprised to see no discussion. I've now lo...