| From: | Kurt Roeckx <kurt(at)roeckx(dot)be> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Gcc 4.4 causes abort in plpython. |
| Date: | 2008-12-29 17:26:34 |
| Message-ID: | 20081229172634.GA26149@roeckx.be |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 29, 2008 at 11:19:56AM -0500, Tom Lane wrote:
> Kurt Roeckx <kurt(at)roeckx(dot)be> writes:
> > On Mon, Dec 29, 2008 at 09:25:47AM -0300, Alvaro Herrera wrote:
> >> I think a simplistic solution is to declare the variable volatile.
> >> Would you test that and report back?
>
> > Yes, making oldcontext volatile makes the test pass.
>
> This is a gcc bug and you should report it. Since the variable is
> not assigned within the try-block, volatile marking should not be
> necessary.
Reported as:
http://gcc.gnu.org/PR38660
kurt
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2008-12-29 17:30:59 | Re: TODO items for window functions |
| Previous Message | Greg Stark | 2008-12-29 17:21:12 | Re: incoherent view of serializable transactions |