X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id E40ADD1B4E3 for ; Thu, 9 Oct 2003 15:35:48 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 52946-10 for ; Thu, 9 Oct 2003 12:35:03 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id AAFC6D1B99F for ; Thu, 9 Oct 2003 12:28:15 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h99FS2u04665; Thu, 9 Oct 2003 11:28:02 -0400 (EDT) From: Bruce Momjian Message-Id: <200310091528.h99FS2u04665@candle.pha.pa.us> Subject: Re: Sun performance - Major discovery! In-Reply-To: To: Jeff Date: Thu, 9 Oct 2003 11:28:01 -0400 (EDT) Cc: Neil Conway , "pgsql-performance@postgresql.org" X-Mailer: ELM [version 2.4ME+ PL106 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/277 X-Sequence-Number: 4025 What is the performance win for the -fast flag again? --------------------------------------------------------------------------- Jeff wrote: > On Thu, 9 Oct 2003, Bruce Momjian wrote: > > > > > So you want -fast added as default for non-gcc Solaris? You mentioned > > there is a warning generated that we have to deal with? > > > > Yeah, suncc generates a warning for _every_ file that says: > Warning: -xarch=native has been explicitly specified, or implicitly > specified by a macro option, -xarch=native on this architecture implies > -xarch=v8plusa which generates code that does not run on pre-UltraSPARC > processors > > And then I get various warnings here and there... > > lots of "statement not reached" as in ecpg's type.c module > The offending code is a big switch statement like: > case ECPGt_bool: > return ("ECPGt_bool"); > break; > > And then any functiont aht uses PG_RETURN_NULL generates " warning: > end-of-loop code not reached" > > and a bunch of "constant promoted to unsigned long long" > > > And some places such as in fe-exec.c have code like this: > buflen = strlen(strtext); /* will shrink, also we discover > if > > where strtext is an unsigned char * which generates warning: argument #1 > is incompatible with prototype: > > and then various other type mismatches here and there. > > I skimmed through the manpage.. it doesn't look like we can supress > these.. > > > Not sure we want it to look like we have bad code if someone uses cc. > perhaps issue a ./configure notice or something? > > gcc compiles things fine. > > > -- > Jeff Trout > http://www.jefftrout.com/ > http://www.stuarthamm.net/ > > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073