search for: pointer_traits_workaround

...885 5455 x116 -- fax: +1 519 885 1463 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090501/a021811f/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: pointer_traits_workaround.diff Type: application/octet-stream Size: 979 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090501/a021811f/attachment.obj> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/att...

...ething else going on I haven't seen yet. I'll look into this some > more as well. > > Let me know if the workaround works for you, and I'd appreciate > feedback from anyone (Chris? Gabor?) as to how best to proceed. > > Thanks! > > Stefanus > > > <pointer_traits_workaround.diff> > > On 1-May-09, at 6:32 AM, Nicolas Capens wrote: > >> Hi all, >> >> I’ve located a regression that causes my project to crash. It’s in >> revision 67979, where PointerIntPair is changed from storing the >> integer in the upper bits instead of th...

Hi all, I've located a regression that causes my project to crash. It's in revision 67979, where PointerIntPair is changed from storing the integer in the upper bits instead of the lower bits. My project is an experimental JIT-compiler in Windows. So I was wondering if anyone had any clue why the new PointerIntPair implementation might fail. It doesn't seem very safe to me to