Paul Eggert wrote: > > --enable-sanitized-realloc change realloc so that it aborts in cases > > of undefined behaviour (experimental) > > Although something along these lines would work, the GNU Coding > Standards say that --enable-* is for user-level facilities, whereas this > is for builders and debuggers. > > --with-* doesn't seem right either.
Oh, you mean this paragraph? You will note that the categories ‘--with-’ and ‘--enable-’ are narrow: they *do not* provide a place for any sort of option you might think of. That is deliberate. We want to limit the possible configuration options in GNU software. We do not want GNU programs to have idiosyncratic configuration options. > Maybe this interim strategy should just be something a builder puts into > CC or CFLAGS? That would better match the proposed long-term strategy > for builders, which is to build with CC="gcc -fsanitize=undefined". Well, if we go for some VARIABLE=VALUE option that is not visible through './configure --help', it could be the name of some cache variable: gl_cv_realloc_sanitize=yes Would that be OK? Bruno
