Date: Tue, 08 May 2001 11:16:36 -0700 From: Jordan Hubbard <jkh@osd.bsdi.com> To: juha@saarinen.org Cc: kris@obsecurity.org, dmmiller@cvzoom.net, msmith@FreeBSD.ORG, nuno.mailinglists@pt-quorum.com, guilherme@nortenet.pt, freebsd-stable@FreeBSD.ORG Subject: RE: CFLAGS Optimization Message-ID: <20010508111636K.jkh@osd.bsdi.com> In-Reply-To: <KPECIILENDDLPCNIMLOFGENOCDAA.juha@saarinen.org> References: <20010508031001.A91590@xor.obsecurity.org> <KPECIILENDDLPCNIMLOFGENOCDAA.juha@saarinen.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> This is "well documented"? It doesn't say *why* optflags above -O are bad. It doesn't really have to. For the newbie user, all it matters is that it instructs them not to do this. It could also add "having the compiler break your code is bad, mmmkay?" but I don't see how that would be anything but a statement of the obvious. For developers, they're expected to play with the flags on a case-by-case basis since only a developer is likely to know whether or not they're doing something dangerous. Can we just drop this already? I think it should be obvious to all concerned at this point that we're not getting anywhere with this thread. If you really want to change things, get off your ass and start coding. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010508111636K.jkh>