From owner-freebsd-hackers@FreeBSD.ORG Thu May 15 07:01:57 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A36C37B411; Thu, 15 May 2003 07:01:57 -0700 (PDT) Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E5C443F75; Thu, 15 May 2003 07:01:56 -0700 (PDT) (envelope-from mooneer@translator.cx) Received: from pool0005.cvx18-bradley.dialup.earthlink.net ([209.179.238.5] helo=morpheus) by falcon.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 19GJIx-00043r-00; Thu, 15 May 2003 07:01:56 -0700 From: "Mooneer Salem" To: , Date: Thu, 15 May 2003 07:01:44 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20030515123033.GP45118@garage.freebsd.pl> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: RE: Optimizations. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2003 14:01:57 -0000 Hello, Interesting. Wouldn't some optimizations only produce negliable results though (in relation to the amount of mess created in the code), especially since PC technology has come a long way? Thanks, -- Mooneer Salem GPLTrans: http://www.translator.cx/ lifeafterking.org: http://www.lifeafterking.org/ -----Original Message----- From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd-hackers@freebsd.org]On Behalf Of Pawel Jakub Dawidek Sent: Thursday, May 15, 2003 5:31 AM To: freebsd-hackers@freebsd.org Cc: freebsd-performance@freebsd.org Subject: Optimizations. Hello hackers... IMHO optimization in FreeBSD's code has too low priority. Maybe is time to think about some 'optimiztion team' creation? It will be a group of hackers that are skilled in using gcc(1) optimiztion flags, when those flags can cause problems and how to slove them (we got -O for years) - optimization flags should be increased just like WARNS value is. They should have experience in old-school optimization (there are many places where '* (2^n)' could be changed to '<< n' and many places where compilator don't know how to or is just unable to optimize, etc.). They could made regular code profiling and present results somewhere (and of course help authors to get better performance in critical places). Bla, bla, bla... Just let's speed-up FreeBSD!. Any opinions/ideas? -- Pawel Jakub Dawidek pawel@dawidek.net UNIX Systems Programmer/Administrator http://garage.freebsd.pl Am I Evil? Yes, I Am! http://cerber.sourceforge.net