Re: Do we need the gcc feature "__builtin_expect" to promote the branches prediction?

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Hao Lee <mixtrue(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Do we need the gcc feature "__builtin_expect" to promote the branches prediction?
Date: 2017-06-06 03:06:55
Message-ID: CAMsr+YGn94r9NXEtgmMATYFaKKd-ndyqpFxzb02Z_8mtU8QCFA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6 June 2017 at 10:44, Hao Lee <mixtrue(at)gmail(dot)com> wrote:
> and another things come into my mind, in some scenario, as we know that the
> native library is not the most effective way to do that, such as, allocation
> a large amount of memories by using "alloc()"... and "memmove()", so on. As
> the SIMD instruction became the standard in CPU, therefore, we can that to
> do something more effectively. for example, using SIMD to impl
> 'alloc',"memmove" and so on, or the other database operations. and it seems
> that there some one have done this job.

Compilers are already pretty good at this.

https://en.wikipedia.org/wiki/Program_optimization

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-06-06 03:09:28 Re: Server ignores contents of SASLInitialResponse
Previous Message Hao Lee 2017-06-06 02:44:03 Re: Do we need the gcc feature "__builtin_expect" to promote the branches prediction?