Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3F09D357.1010901@cern.ch> Date: Mon, 07 Jul 2003 22:08:55 +0200 From: "Lassi A. Tuura" Organization: Northeastern University, Boston, USA User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030401 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin Gainty CC: cygwin@cygwin.com Subject: Re: restrict References: In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > I have never seen restrict keyword..any ideas? It was introduced in C99, and in a few compilers before that. Roughly speaking it means the memory pointed to by the restrict pointer is not aliased by anything else visible in that scope, so the compiler is free to optimise the code assuming no other pointer write writes over memory. Take for example: int foo (int *restrict a, int *restrict b) { a[1] = b[1]; return b[0] + a[1]; } The compiler can assume the assignment to a[1] will not have modified b[0]. Hope this helps, //lat -- The stone fell on the pitcher? Woe to the pitcher. The pitcher fell on the stone? Woe to the pitcher. --Rabbinic Sayning -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/