[ub] [c++std-ext-14579] Re: Sized integer types and char bits

Lawrence Crowl Lawrence at Crowl.org
Thu Oct 24 09:14:30 CEST 2013


On 10/23/13, Gabriel Dos Reis <gdr at microsoft.com> wrote:
> For instance, what we lose if we go from undefined behavior to
> unspecified?  E.g. the behavior on erroneous construct isn't unrestricted
> yet allow for tools to instrument and/or report?

I think we lose some optimization opportunity when switching from
undefined to unspecified, so we might want to be careful about where
we use each term.  As near as I can tell, the difference between the
two terms does not affect programs trying for maximum portability.

-- 
Lawrence Crowl


More information about the ub mailing list