Re: Auto-vectorization speeds up multiplication of large-precision numerics

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Auto-vectorization speeds up multiplication of large-precision numerics
Date: 2020-07-10 13:32:10
Message-ID: 2055072.1594387930@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> We normally don't compile with -O3, so very few users would get the
> benefit of this.

Yeah. I don't think changing that baseline globally would be a wise move.

> We have CFLAGS_VECTOR for the checksum code. I
> suppose if we are making the numeric code vectorizable as well, we
> should apply this there also.

> I think we need a bit of a policy decision from the group here.

I'd vote in favor of applying CFLAGS_VECTOR to specific source files
that can benefit. We already have experience with that and we've not
detected any destabilization potential.

(I've not looked at this patch, so don't take this as a +1 for this
specific patch.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-07-10 13:35:56 Re: pg_regress cleans up tablespace twice.
Previous Message Peter Eisentraut 2020-07-10 13:30:07 Re: Default gucs for EXPLAIN