pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Jeff <threshar@torgo.978.org>
Cc: Neil Conway <neilc@samurai.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Sun performance - Major discovery!
Date: Thu, 9 Oct 2003 11:28:01 -0400 (EDT)
Message-ID: <200310091528.h99FS2u04665@candle.pha.pa.us> (raw)
In-Reply-To: <Pine.BSF.4.44.0310091044450.69724-100000@torgo.978.org>


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 <jeff@jefftrout.com>
> 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



view thread (48+ messages)  latest in thread

Message-ID: <200310091528.h99FS2u04665@candle.pha.pa.us>
Permalink:  ../200310091528.h99FS2u04665@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200310091528.h99FS2u04665@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: pgman@candle.pha.pa.us, threshar@torgo.978.org, neilc@samurai.com
  Subject: Re: Sun performance - Major discovery!
  In-Reply-To: <200310091528.h99FS2u04665@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox