From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,22d1652a85f14a1e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-02-27 10:49:03 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!lnsnews.lns.cornell.edu!news.litech.org!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.freenet.de!213.253.16.105.MISMATCH!mephistopheles.news.clara.net!news.clara.net!feed.news.nacamar.de!newsfeed01.sul.t-online.de!newsmm00.sul.t-online.com!t-online.de!news.t-online.com!not-for-mail From: Alfred Hilscher Newsgroups: comp.lang.ada Subject: Re: Speeding up Ada procedure? Date: Thu, 27 Feb 2003 19:43:50 +0100 Organization: T-Online Message-ID: <3E5E5C66.E2FA8021@t-online.de> References: <1d13e1b4.0302261526.40058154@posting.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.t-online.com 1046371665 06 1175 EJpPEHBSXaYLS 030227 18:47:45 X-Complaints-To: abuse@t-online.com X-Sender: 320001779794-0001@t-dialin.net X-Mailer: Mozilla 4.75 [de] (WinNT; U) X-Accept-Language: de Xref: archiver1.google.com comp.lang.ada:34685 Date: 2003-02-27T19:43:50+01:00 List-Id: Papandopulo schrieb: > > I have certain procedures dealing with > large arrays which are potential performance > bottlenecks. While they didn't cause > performance problems yet I intuitively > feel they will. I did performance measurement and improvements as my job for many years. Experience showed that the problems often (nearly always) occured where they were _not_ expected. So I would suggest to do some measurements first. You can do this with GNAT very easy by running gprof. > Is it a way to remove runtime array > bounds and other checks for particular > procedure ? If it is assured that really the arrays are the problem then this could be a way, but there raises the danger of (C-like) "buffer overflows".