search for: restricts

Displaying 20 results from an estimated 15050 matches for "restricts".

Did you mean: restrict
2018 Feb 14
1
[vhost:vhost 22/23] drivers/firmware/qemu_fw_cfg.c:130:36: sparse: incorrect type in initializer (different base types)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost head: 3d22d7c1190db3209b644b8a13a75a9802b4587f commit: b3a8771f409b74c42deee28aee3092fc5d2c8dab [22/23] fw_cfg: write vmcoreinfo details reproduce: # apt-get install sparse git checkout b3a8771f409b74c42deee28aee3092fc5d2c8dab make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__
2007 Aug 26
1
[LLVMdev] c const
Hi Daniel, On Aug 24, 2007, at 10:20 AM, Daniel Berlin wrote: > On 8/22/07, Christopher Lamb <christopher.lamb at gmail.com> wrote: >> >> >> 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
2007 Aug 24
0
[LLVMdev] c const
On 8/22/07, Christopher Lamb <christopher.lamb at gmail.com> wrote: > > > 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
2007 Aug 22
2
[LLVMdev] c const
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 >>
2020 Feb 14
2
Given one restrict pointer based on another, should they never alias?
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 they never alias? As far as I understand the
2020 Feb 20
2
Given one restrict pointer based on another, should they never alias?
Thanks, Jeroen, that really helps. 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
2018 Aug 17
2
alias.scope and local restricted C pointers
...>> that https://llvm.org/docs/LangRef.html#noalias-and-alias-scope-metadata should >> be sufficiently general to honor C’s restrict qualifier on local >> pointers, >> but it does not appear that Clang uses this part of LLVM’s IR for >> that purpose today and thus local restricts are ignored. > > I think that’s correct, but I haven’t come out with any scenarios > regarding local variables/memory that can _not_ be solved by AA. As > BasicAA is able to solved most of the local cases, including malloc > and some memory intrinsics. int *restrict x = some_externa...
2007 Mar 26
6
[LLVMdev] C99 restrict
On Mar 26, 2007, at 10:10 AM, Dan Gohman wrote: > On Mon, Mar 26, 2007 at 02:14:56AM -0500, Christopher Lamb wrote: >> >> >> On Mar 25, 2007, at 5:22 PM, Chris Lattner wrote: >> >>> On Sun, 25 Mar 2007, Christopher Lamb wrote: >>>> What about an approach not unlike how debugging information is >>>> handled? That >>>> is have
2012 Dec 03
2
[LLVMdev] [RFC] Scoped no-alias metadata
----- Original Message ----- > From: "Daniel Berlin" <dberlin at dberlin.org> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "Chandler Carruth" <chandlerc at google.com>, "Clang Developers" <cfe-dev at cs.uiuc.edu>, "LLVM Developers Mailing > List" <llvmdev at cs.uiuc.edu> > Sent: Sunday, December 2, 2012
2017 Sep 12
4
File server questions
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
2012 Dec 03
3
[LLVMdev] [RFC] Scoped no-alias metadata
----- Original Message ----- > From: "Chandler Carruth" <chandlerc at google.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>, "Clang Developers" <cfe-dev at cs.uiuc.edu>, "Dan Gohman" > <dan433584 at gmail.com> > Sent: Sunday, December 2, 2012
2012 Dec 03
0
[LLVMdev] [RFC] Scoped no-alias metadata
On Sun, Dec 2, 2012 at 8:05 PM, Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- >> From: "Chandler Carruth" <chandlerc at google.com> >> To: "Hal Finkel" <hfinkel at anl.gov> >> Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>, "Clang Developers" <cfe-dev at cs.uiuc.edu>,
2015 Feb 09
1
member ntp time sync
On my member server, running 'ntpq -p' yields: ntpq -p localhost: timed out, nothing received ***Request timed out The ntp.conf file is trying to use the DC's hostnames addresses: user at DC01:~# cat /etc/ntp.conf # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help driftfile /var/lib/ntp/ntp.drift # Enable this if you want statistics to be logged. #statsdir
2020 May 05
1
[Bug 3159] New: authorized_keys: gap in port forwarding restrictions
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
2012 Dec 03
0
[LLVMdev] [RFC] Scoped no-alias metadata
On Mon, Dec 3, 2012 at 6:19 AM, Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- >> From: "Daniel Berlin" <dberlin at dberlin.org> >> To: "Hal Finkel" <hfinkel at anl.gov> >> Cc: "Chandler Carruth" <chandlerc at google.com>, "Clang Developers" <cfe-dev at cs.uiuc.edu>, "LLVM
2012 Dec 03
2
[LLVMdev] [RFC] Scoped no-alias metadata
----- Original Message ----- > From: "Daniel Berlin" <dberlin at dberlin.org> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "Chandler Carruth" <chandlerc at google.com>, "Clang Developers" <cfe-dev at cs.uiuc.edu>, "LLVM Developers Mailing > List" <llvmdev at cs.uiuc.edu> > Sent: Monday, December 3, 2012
2005 Apr 27
1
Guest user?
Hello all, Am trying to set up a guest account for employees from other offices to come in the office to login 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
2018 Aug 16
3
alias.scope and local restricted C pointers
...ement still accurate? It would seem that https://llvm.org/docs/LangRef.html#noalias-and-alias-scope-metadata should be sufficiently general to honor C's restrict qualifier on local pointers, but it does not appear that Clang uses this part of LLVM's IR for that purpose today and thus local restricts are ignored. Thanks, Troy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180816/856426e5/attachment.html>
2007 Mar 26
3
[LLVMdev] C99 restrict
On Mar 25, 2007, at 5:22 PM, Chris Lattner wrote: > On Sun, 25 Mar 2007, Christopher Lamb wrote: >>> So far, there hasn't been a discussion. IMO, the most important >>> form is >>> for formal arguments. That could easily be added thorough the >>> use of an >>> attribute on the parameter. >> >> I assume the idea here is to
2023 Oct 25
3
DC Time Problems
It appears that none of our windows clients are syncing their time with the samba DC.??? From what I can tell they are not able to get a response from the DC.? For example, where the DC is named athena: >w32tm /monitor /computers:athena athena[10.10.1.10:123] ? ICMP: 0ms delay ? NTP: error ERROR_TIMEOUT - no response from server in 1000ms From a Linux machine there is