Re: gcc -O2 produces invalid object code (x86_64, netbsd-5 branch)

[Joerg Sonnenberger <joerg%britannica.bec.de@localhost>]

On Mon, Mar 08, 2010 at 10:33:52AM -0500, Richard Hansen wrote:
> So the bug isn't in gcc, it's in openpam:  either the pam_end(3) man
> page should be updated to say that pamh must be non-NULL, or the
> attribute should be removed from the declaration.  Which do people
> prefer?

I still don't get what makes you point your finger at random stuff and
complain that it is broken. What did you do to make pam_start return
success and NULL in *pamh?

Joerg