From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Xi Wang <xi(dot)wang(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [RFC] overflow checks optimized away |
Date: | 2015-12-01 17:17:21 |
Message-ID: | CAM-w4HOtOVHt=Ez-BvKw6-q-+OE7wQDNsxssRuf4vwr535X_Ug@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Oct 9, 2015 at 2:52 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Any news on this item from 2013, worked on again 2014?
>
Sorry, I didn't look at it since. At the time I was using Xi Wang's
software to find the overflow checks that need to be redone. He published a
paper on it and it's actually pretty impressive. It constructs a constraint
problem and then throws a kSAT solver at it to find out if there's any code
that a compiler could optimize away regardless of whether any existant
compiler is actually capable of detecting the case and optimizing it away.
https://pdos.csail.mit.edu/papers/stack:sosp13.pdf
Xi Wang actually went on to pursue the same issues in the Linux kernel,
Clang, and elsewhere:
https://css.csail.mit.edu/stack/
http://kqueue.org/blog/2012/03/16/fast-integer-overflow-detection/
http://lists.llvm.org/pipermail/cfe-commits/Week-of-Mon-20130617/082221.html
I'm up for trying again but it's a long slong to replace all the overflow
checks and the patch will be big....
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-12-01 17:38:34 | Re: gincostestimate and hypothetical indexes |
Previous Message | Tom Lane | 2015-12-01 17:07:28 | Re: Foreign join pushdown vs EvalPlanQual |