Re: v13: Performance regression related to FORTIFY_SOURCE

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Peter Geoghegan <pg(at)bowt(dot)ie>
Subject: Re: v13: Performance regression related to FORTIFY_SOURCE
Date: 2020-06-06 01:46:13
Message-ID: bf0f36bcb9e2d7995da302cdde221e339a74bfe0.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2020-06-04 at 16:35 -0400, Alvaro Herrera wrote:
> If it is something worth worrying about, let's discuss what's a good
> fix for it.

While making a minimal test case for the GCC bug report, I found
another surprisingly-small workaround. Patch attached.

Regards,
Jeff Davis

Attachment Content-Type Size
memcpy-workaround.patch text/x-patch 527 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-06-06 01:50:53 Re: v13: Performance regression related to FORTIFY_SOURCE
Previous Message Jeff Davis 2020-06-06 01:39:28 Re: v13: Performance regression related to FORTIFY_SOURCE