------- Comment #3 from dgohman at gmail dot com 2010-06-08 14:54 ------- Callers of compare are already exposed to __builtin_memcmp result values (with default traits) which vary depending on the target and compiler flags.
And since _S_compare is only used as a tie-breaker after the memcmp, it's hard to imagine any code innocently relying on it returning a particular value. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44413
