The question "Why must glibc be compiled with optimizations enabled?" comes up often on the mailing list. The following patch adds an answer to the FAQ.
Created attachment 1992 [details] Add FAQ entry: Why must glibc be compiled with optimizations enabled?
Comments? OK to checkin?
This comment is not complete. There are other reasons. For instance, nested functions must be inlined in many cases to avoid executable stacks.
patch checked into glibc head.
Created attachment 2239 [details] Add FAQ entry: Why must glibc be compiled with optimizations enabled?
It doesn't look like this was ever checked into glibc head? I've updated the patch to include Ulrich's comments about nested functions. OK to checkin?
Ping?
Andreas, I don't see that this was checked in?
Subject: Bug 5012 CVSROOT: /cvs/glibc Module name: libc Changes by: aj@sourceware.org 2008-02-22 09:57:19 Modified files: . : FAQ.in Log message: [BZ #5012] * FAQ.in: Describe why glibc needs to be compiled with optimization. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/libc/FAQ.in.diff?cvsroot=glibc&r1=1.138&r2=1.139
I now checked the version in which was posted here: http://sourceware.org/ml/libc-hacker/2007-10/msg00023.html Thanks Carlos!