search for: estrict

...ke how debugging information is >> handled? That >> is have an llvm intrinsic that encodes the known alias free range >> for a >> pointer. > > That is another great possibility. One issue is that I haven't had > time > to study the implications of C99 restrict, so I don't feel > qualified to > propose a concrete solution yet. Ideally, the mechanism added to LLVM > would be able to handle restrict as well as fortran argument > parameters > (even if the fortran functions are inlined!), etc. IOW, we don't > want to > hav...

...gt;> handled? That > >> is have an llvm intrinsic that encodes the known alias free range > >> for a > >> pointer. > > > > That is another great possibility. One issue is that I haven't had > > time > > to study the implications of C99 restrict, so I don't feel > > qualified to > > propose a concrete solution yet. Ideally, the mechanism added to LLVM > > would be able to handle restrict as well as fortran argument > > parameters > > (even if the fortran functions are inlined!), etc. IOW, we don'...

...DRI status is given here and shows that the second video card (card1) is not set to any PCI bus: dristat -a /dev/dri/card0 Busid: pci:0000:03:00.0 Version information: Name: nouveau Version: 1.0.0 Date: 20120316 Desc: nVidia Riva/TNT/GeForce VM map information: flags: (R)estricted (r)ead/(w)rite (l)ocked (k)ernel (W)rite-combine (L)ock: slot offset size type flags address mtrr 0 0x11839000 0x00002000 SHM w L 0x1b7ff000 none DRI client information: a pid uid magic ioctls prog y 1482 0 0 7 dristat...

..., exactly. > What about an approach not unlike how debugging information is handled? That > is have an llvm intrinsic that encodes the known alias free range for a > pointer. That is another great possibility. One issue is that I haven't had time to study the implications of C99 restrict, so I don't feel qualified to propose a concrete solution yet. Ideally, the mechanism added to LLVM would be able to handle restrict as well as fortran argument parameters (even if the fortran functions are inlined!), etc. IOW, we don't want to have an feature that just implements C99...

On Mar 25, 2007, at 2:18 AM, Chris Lattner wrote: > On Sat, 24 Mar 2007, Christopher Lamb wrote: >> Has there been any discussion of supporting the 'restrict' C99 >> keyword >> and C++ extension to boost alias analysis? My impression is that this >> would require modification of the LLVM IR. I couldn't find any >> discussion hits using the usual suspects for searches... > > So far, there hasn't been a discussi...

...That >>>> is have an llvm intrinsic that encodes the known alias free range >>>> for a >>>> pointer. >>> >>> That is another great possibility. One issue is that I haven't had >>> time >>> to study the implications of C99 restrict, so I don't feel >>> qualified to >>> propose a concrete solution yet. Ideally, the mechanism added to >>> LLVM >>> would be able to handle restrict as well as fortran argument >>> parameters >>> (even if the fortran functions are inlined...