why Glibc does not build with clang?

Rich Felker dalias@libc.org
Sat May 24 16:22:00 GMT 2014


On Sat, May 24, 2014 at 06:11:50PM +0200, Andreas Schwab wrote:
> Rich Felker <dalias@libc.org> writes:
> 
> > On Sat, May 24, 2014 at 04:46:03PM +0200, Andreas Schwab wrote:
> >> Rich Felker <dalias@libc.org> writes:
> >> 
> >> > Nested functions are a feature that fundamentally requires producing
> >> > an insecure executable/library (executable-stack flag)
> >> 
> >> Only if you pass the address of it out of the containing function.
> >
> > That's my "_except_ in cases where the compiler optimizes out that
> > need."
> 
> That's not the exception, that's the rule.  If you never take the
> address of the nested function you never need a trampoline.

"If you only use feature X in one particular way" (versus in full
generality, using it any way you can use a function) I call that an
exception to the rule, not the general case. But this has devolved to
a pointless discussion of the meaning of "exception".

Rich



More information about the Libc-alpha mailing list