Subject: port-powerpc/29746: db4 still suffers from gcc 3.3 optimization bug on powerpc
To: None <,,>
From: None <>
List: netbsd-bugs
Date: 03/20/2005 10:28:00
>Number:         29746
>Category:       port-powerpc
>Synopsis:       db4 still suffers from gcc 3.3 optimization bug on powerpc
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    port-powerpc-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Mar 20 10:28:00 +0000 2005
>Originator:     Timo Schoeler
>Release:        NetBSD 2.0/macppc
NetBSD 2.0 NetBSD 2.0 (GENERIC.MP) #0: Wed Dec  1 14:05:26 UTC 2004  builds@build:/big/builds/ab/netbsd-2-0-RELEASE/macppc/200411300000Z-obj/big/builds/ab/netbsd-2-0-RELEASE/src/sys/arch/macppc/compile/GENERIC.MP macppc
as stated in pkgsrc/databases/db4/, this small hack solves PR 23737:

### [Sun Mar 14 19:32:40 UTC 2004 : jlam]
### Pre-3.3 GCC has an optimization bug on powerpc that's tickled by
### the db4 source code, so remove optimization flags in that case.
### This fixes PR 23737 by John Klos.

*it does not*

i built db-4.3.27 yesterday with the on-board compiler of NetBSD 2.0 (which is gcc 3.3.3) and run into a non-functioning cyrus-imapd which stated a cyrus-killing database failure in /var/log/messages.

trying the binary package from -- it runs. i'm building gcc 3.4.3 right now to see if this solves the problem.

but still, the gcc 3.3.3 issue remains.
build db4 with the on-board gcc (which is 3.3.3) and watch it fail (e.g. by using it as backend for the cyrus-imapd).
unfortunately not