| From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Postgres Hackers List <hackers(at)postgresql(dot)org> |
| Subject: | Platforms with v6.3 trouble |
| Date: | 1998-02-25 14:28:37 |
| Message-ID: | 34F42A95.E5D12A02@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>From what I understand, there are at least two platforms which are
having trouble with the macro inlining in v6.3. The alpha ports have
trouble inlining the slock assembler code, and the SCO port has trouble
inlining the cache lookup code.
Since these macros were inlined only for performance reasons, would it
be possible to revert to non-inline function calls for these platforms?
It would seem that substituting a macro expansion for a compiled routine
could be done with a compiler switch (e.g. USE_INLINING) so it could be
turned on and off at will.
For most of us, the performance gains are fantastic, but for those ports
which broke performance has degraded to zero :(
- Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-02-25 14:29:03 | Re: [QUESTIONS] How fully will subselects be implemented? |
| Previous Message | Jan Wieck | 1998-02-25 14:28:26 | Re: [HACKERS] Re: [PATCHES] pg_shadow |