* Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > > In that sense ((section)) is way more robust: there's not really that many > > ways to screw that up. Fiddling with the ((constructor)) environment on the > > other hand ... > > Sorry, this is textbook FUD. I specifically cited the problem of static libraries. They *do not work* with ((constructor)). That's not FUD but justified scepticism backed by hard evidence. > > __attribute__((constructor)) is not particularly portable to begin with: > > does the MSVC compiler support it for example? > > No, but GCC supports it on non-ELF platforms, [...] So you claim that ((section)) is 'not portable' but concede that it does in fact not port to one of the most widely used compilers. Instead you clarify that under 'not portable' you really meant to say that ((section)) does not work on non-ELF binary platforms. That is a pretty inconsistent position and has nothing to do with 'portability' in itself but with being portable to what *you* consider important. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
