| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-patches(at)postgresql(dot)org, Neil Conway <neilc(at)samurai(dot)com>, Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>, korryd(at)enterprisedb(dot)com, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: [pgsql-patches] Patch to avoid gprof profilingoverwrites |
| Date: | 2007-02-01 14:33:15 |
| Message-ID: | 17698.1170340395@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Neil Conway wrote:
>> What about a "--enable-gprof" (or "--enable-profiling"?) configure
>> flag? This could add the appropriate compiler flags to CFLAGS, enable
>> LINUX_PROFILE if on Linux, and enable the "gprof/pid" mkdir().
> That would really only work for GCC, wouldn't it?
Well, yeah, but that's what many of us use anyway. I would envision it
as adding $(PROFILE) to CFLAGS, and then there would be one place
to adjust "-pg" to something else for another compiler --- perhaps the
template files could be given a chance to change PROFILE to something
else.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | korryd | 2007-02-01 15:52:07 | Re: [pgsql-patches] Patch to avoid gprofprofilingoverwrites |
| Previous Message | korryd | 2007-02-01 14:19:53 | Re: [pgsql-patches] Patch to avoid gprofprofilingoverwrites |