search for: restrict

...etails reproduce: # apt-get install sparse git checkout b3a8771f409b74c42deee28aee3092fc5d2c8dab make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__ sparse warnings: (new ones prefixed by >>) drivers/firmware/qemu_fw_cfg.c:108:28: sparse: cast to restricted __be32 drivers/firmware/qemu_fw_cfg.c:108:28: sparse: cast to restricted __be32 drivers/firmware/qemu_fw_cfg.c:108:28: sparse: cast to restricted __be32 drivers/firmware/qemu_fw_cfg.c:108:28: sparse: cast to restricted __be32 drivers/firmware/qemu_fw_cfg.c:108:28: sparse: cast to rest...

...t;> they evaluate to a value of the pointed-to type rather than a >> pointer to the >> type. Only pointers may be "based on" other pointers from my >> reading of the >> spec. > > Christopher, just to point something out. > > Earlier you said that restrict says something about the relationship > of a pointer to non-restricted pointers. This is not true except for > one small case. > Restricted pointers in general only tell you things about a > relationship to other restricted pointers. I'm not sure which previous statement was uncle...

...ou mention are indeed not pointer expressions as > they evaluate to a value of the pointed-to type rather than a pointer to the > type. Only pointers may be "based on" other pointers from my reading of the > spec. Christopher, just to point something out. Earlier you said that restrict says something about the relationship of a pointer to non-restricted pointers. This is not true except for one small case. Restricted pointers in general only tell you things about a relationship to other restricted pointers. IE the following is perfectly legal: int foo(int *a, restrict int *b)...

On Aug 22, 2007, at 3:48 PM, Duncan Sands wrote: > Hi Christopher, > >> If A and B are function arguments then there is no "based on" >> relationship between pointer expressions A+0 and B+0. This is because >> changing one of the pointers, A for example, to point to a copy of >> the object it points to would change the value of the pointer >>

We recently found an issue when using the full restrict implementation developed by Jeroen; it surfaces when compiling an obscure combination of std::valarray and std::indirect_array but I don't want to bore you with all the details. What it boils down to is this basic question about restrict: Given one restrict pointer based on another, should the...

...elps. A follow-up question, if you don't mind. What if we have code somewhat similar to your example in assign3() but it's in C++ and the pointer derived from x is stored in a class member field: class S { public: S(int *d): data(d) {} int *getData() { return data; } private: int *__restrict__ data; }; void assign4(int *pA, long N) { int *__restrict__ x = pA; int tmp; { S s(x + N); tmp = *s.getData(); } *x = tmp; } I see that the full restrict implementation says that the load and the store do not alias. Is this by design? On Sat, Feb 15, 2020 at 9:00 AM Jeroen Do...

...18 07:52 PM, Bekket McClane via llvm-dev wrote: > > >> On Aug 16, 2018, at 4:41 PM, Troy Johnson via llvm-dev >> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> Concerning slide 16 >> of https://llvm.org/devmtg/2017-02-04/Restrict-Qualified-Pointers-in-LLVM.pdf >>   >> Specifically “Currently, LLVM only supports restrict on function >> arguments, although we have a way to preserve that information if the >> function is inlined.” >>   >> Is that statement still accurate?  > > Yes, cor...

...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...

...kel < hfinkel at anl.gov > > >> wrote: > >> > >> > >> > >> > >> Hello, > >> > >> I'd like to propose a new form of memory-aliasing metadata: scoped > >> no-alias metadata. This can be used to model local 'restrict' > >> pointers in C99, but should also be useful for other frontends (I > >> think, for example, that Fortran will want this as well). > >> Currently, > >> we only use the restrict qualifier on function arguments in Clang > >> where we translate the...

On Tue, 12 Sep 2017 14:41:42 -0300 Flávio Silveira via samba <samba at lists.samba.org> wrote: > > Ok, I understand now, one question though: if realm is > AD.TECNOPON.COM.BR, does domain need to be AD? No, you can use anything you like, provided it is one word, 15 characters or less, without punctuation. > If I understand > correctly, realm is "full domain with

...ias metadata > > > > On Sun, Dec 2, 2012 at 12:48 PM, Hal Finkel < hfinkel at anl.gov > > wrote: > > > > > Hello, > > I'd like to propose a new form of memory-aliasing metadata: scoped > no-alias metadata. This can be used to model local 'restrict' > pointers in C99, but should also be useful for other frontends (I > think, for example, that Fortran will want this as well). Currently, > we only use the restrict qualifier on function arguments in Clang > where we translate the restrict qualifier as a 'noalias' function...

...> On Sun, Dec 2, 2012 at 12:48 PM, Hal Finkel < hfinkel at anl.gov > >> wrote: >> >> >> >> >> Hello, >> >> I'd like to propose a new form of memory-aliasing metadata: scoped >> no-alias metadata. This can be used to model local 'restrict' >> pointers in C99, but should also be useful for other frontends (I >> think, for example, that Fortran will want this as well). Currently, >> we only use the restrict qualifier on function arguments in Clang >> where we translate the restrict qualifier as a 'noali...

...server 0.debian.pool.ntp.org iburst server 1.debian.pool.ntp.org iburst server 2.debian.pool.ntp.org iburst server 3.debian.pool.ntp.org iburst # Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for # details. The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions> # might also be helpful. # # Note that "restrict" applies to both servers and clients, so a configuration # that might be intended to block requests from certain clients could also end # up blocking replies from your own upstream servers. # By default, exchange time with everybod...

https://bugzilla.mindrot.org/show_bug.cgi?id=3159 Bug ID: 3159 Summary: authorized_keys: gap in port forwarding restrictions Product: Portable OpenSSH Version: 8.0p1 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org Reporter: spmfox at...

...;> >> wrote: >> >> >> >> >> >> >> >> >> >> Hello, >> >> >> >> I'd like to propose a new form of memory-aliasing metadata: scoped >> >> no-alias metadata. This can be used to model local 'restrict' >> >> pointers in C99, but should also be useful for other frontends (I >> >> think, for example, that Fortran will want this as well). >> >> Currently, >> >> we only use the restrict qualifier on function arguments in Clang >> >> whe...

...> > >> >> > >> >> > >> >> Hello, > >> >> > >> >> I'd like to propose a new form of memory-aliasing metadata: > >> >> scoped > >> >> no-alias metadata. This can be used to model local 'restrict' > >> >> pointers in C99, but should also be useful for other frontends > >> >> (I > >> >> think, for example, that Fortran will want this as well). > >> >> Currently, > >> >> we only use the restrict qualifier on functi...

...and do stuff. I want to block access to all public drives so this is what I've done: Consider the SAMBA server in Office A and I want to create a guest account so that people from Office B and C can access. There is a public drive that everyone in Office A can edit, and a drive called "Restricted" that one person in Office A can edit, but everyone else in Office A can access but not edit. Created a group called "everyone" and added everyone in Office A to that group Created a group called "Restricted" and added the person who's allowed to edit this drive to t...

Concerning slide 16 of https://llvm.org/devmtg/2017-02-04/Restrict-Qualified-Pointers-in-LLVM.pdf Specifically "Currently, LLVM only supports restrict on function arguments, although we have a way to preserve that information if the function is inlined." Is that statement still accurate? It would seem that https://llvm.org/docs/LangRef.html#noalias-an...

...ike 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...

...eve the time from server 0.pool.ntp.org???? iburst prefer server 1.pool.ntp.org???? iburst prefer server 2.pool.ntp.org???? iburst prefer driftfile?????? /var/lib/ntpsec/ntp.drift logfile???????? /var/log/ntp.log #logconfig =all ntpsigndsocket? /var/lib/samba/ntp_signd/ # Access control # Default restriction: Allow clients only to query the time #restrict default kod nomodify notrap nopeer limited mssntp restrict -4 default kod limited nomodify notrap nopeer noquery mssntp # No restrictions for "localhost" restrict 127.0.0.1 # Enable the time sources to only provide time to this host restr...