search for: r274656

...s. - BasicAA and other stuff are marked (by overriding `invalidate` to return false) to never be invalidated because they are "stateless". However they still hold pointers and so they do need to be invalidated. - CallGraph uses AssertingVH (PR28400) and so I needed a workaround similar to r274656 in various passes. - D21921 is holding up -- I haven't hit any issues with the core logic of that patch. - AAResults holds handles to various AA result objects. This means it pretty much always needs to be invalidated unless you are sure that none of the AA's will get invalidated. The exi...

...ked (by overriding `invalidate` to >> return false) to never be invalidated because they are "stateless". However >> they still hold pointers and so they do need to be invalidated. >> - CallGraph uses AssertingVH (PR28400) and so I needed a workaround >> similar to r274656 in various passes. >> - D21921 is holding up -- I haven't hit any issues with the core logic >> of that patch. >> - AAResults holds handles to various AA result objects. This means it >> pretty much always needs to be invalidated unless you are sure that none of >>...

...invalidate` to > > return false) to never be invalidated because they are "stateless". > > However they still hold pointers and so they do need to be > > invalidated. > > > - CallGraph uses AssertingVH (PR28400) and so I needed a workaround > > similar to r274656 in various passes. > > > - D21921 is holding up -- I haven't hit any issues with the core > > logic of that patch. > > > - AAResults holds handles to various AA result objects. This means > > it > > pretty much always needs to be invalidated unless you are...

...tateless". > > > > However they still hold pointers and so they do need to be > > > > invalidated. > > > > > > > > > > - CallGraph uses AssertingVH (PR28400) and so I needed a > > > > workaround > > > > similar to r274656 in various passes. > > > > > > > > > > - D21921 is holding up -- I haven't hit any issues with the > > > > core > > > > logic of that patch. > > > > > > > > > > - AAResults holds handles to various AA resu...

...tateless". > > > > However they still hold pointers and so they do need to be > > > > invalidated. > > > > > > > > > > - CallGraph uses AssertingVH (PR28400) and so I needed a > > > > workaround > > > > similar to r274656 in various passes. > > > > > > > > > > - D21921 is holding up -- I haven't hit any issues with the > > > > core > > > > logic of that patch. > > > > > > > > > > - AAResults holds handles to various AA resu...

...tateless". > > > > However they still hold pointers and so they do need to be > > > > invalidated. > > > > > > > > > > - CallGraph uses AssertingVH (PR28400) and so I needed a > > > > workaround > > > > similar to r274656 in various passes. > > > > > > > > > > - D21921 is holding up -- I haven't hit any issues with the > > > > core > > > > logic of that patch. > > > > > > > > > > - AAResults holds handles to various AA resu...

...ng `invalidate` to >>> return false) to never be invalidated because they are "stateless". However >>> they still hold pointers and so they do need to be invalidated. >>> - CallGraph uses AssertingVH (PR28400) and so I needed a workaround >>> similar to r274656 in various passes. >>> - D21921 is holding up -- I haven't hit any issues with the core logic >>> of that patch. >>> - AAResults holds handles to various AA result objects. This means it >>> pretty much always needs to be invalidated unless you are sure that...

...to >>>> return false) to never be invalidated because they are "stateless". However >>>> they still hold pointers and so they do need to be invalidated. >>>> - CallGraph uses AssertingVH (PR28400) and so I needed a workaround >>>> similar to r274656 in various passes. >>>> - D21921 is holding up -- I haven't hit any issues with the core logic >>>> of that patch. >>>> - AAResults holds handles to various AA result objects. This means it >>>> pretty much always needs to be invalidated unless yo...

...to >>>> return false) to never be invalidated because they are "stateless". However >>>> they still hold pointers and so they do need to be invalidated. >>>> - CallGraph uses AssertingVH (PR28400) and so I needed a workaround >>>> similar to r274656 in various passes. >>>> - D21921 is holding up -- I haven't hit any issues with the core logic >>>> of that patch. >>>> - AAResults holds handles to various AA result objects. This means it >>>> pretty much always needs to be invalidated unless yo...

...rn false) to never be invalidated because they are "stateless". However >>>>>> they still hold pointers and so they do need to be invalidated. >>>>>> - CallGraph uses AssertingVH (PR28400) and so I needed a workaround >>>>>> similar to r274656 in various passes. >>>>>> - D21921 is holding up -- I haven't hit any issues with the core >>>>>> logic of that patch. >>>>>> - AAResults holds handles to various AA result objects. This means it >>>>>> pretty much always n...

...never be invalidated because they are "stateless". However >>>>>>> they still hold pointers and so they do need to be invalidated. >>>>>>> - CallGraph uses AssertingVH (PR28400) and so I needed a workaround >>>>>>> similar to r274656 in various passes. >>>>>>> - D21921 is holding up -- I haven't hit any issues with the core >>>>>>> logic of that patch. >>>>>>> - AAResults holds handles to various AA result objects. This means >>>>>>> it pret...

On Wed, Jul 13, 2016 at 12:25 AM Sean Silva <chisophugis at gmail.com> wrote: > On Tue, Jul 12, 2016 at 11:39 PM, Chandler Carruth <chandlerc at gmail.com> > wrote: > >> On Tue, Jul 12, 2016 at 11:34 PM Sean Silva <chisophugis at gmail.com> >> wrote: >> >>> On Tue, Jul 12, 2016 at 11:32 PM, Xinliang David Li <davidxl at google.com>

...validated because they are "stateless". However >>>>>>>> they still hold pointers and so they do need to be invalidated. >>>>>>>> - CallGraph uses AssertingVH (PR28400) and so I needed a workaround >>>>>>>> similar to r274656 in various passes. >>>>>>>> - D21921 is holding up -- I haven't hit any issues with the core >>>>>>>> logic of that patch. >>>>>>>> - AAResults holds handles to various AA result objects. This means >>>>>>...

...are marked (by overriding `invalidate` to return false) to never be invalidated because they are "stateless". However they still hold pointers and so they do need to be invalidated. >>>>>>> - CallGraph uses AssertingVH (PR28400) and so I needed a workaround similar to r274656 in various passes. >>>>>>> - D21921 is holding up -- I haven't hit any issues with the core logic of that patch. >>>>>>> - AAResults holds handles to various AA result objects. This means it pretty much always needs to be invalidated unless you are sure...