C++ Logo

SG12

Advanced search

Subject: Re: [ub] Sized integer types and char bits
From: Gabriel Dos Reis (gdr_at_[hidden])
Date: 2013-10-24 02:25:06


| -----Original Message-----
| From: ub-bounces_at_[hidden] [mailto:ub-bounces_at_[hidden]] On Behalf Of
| Lawrence Crowl
| Sent: Thursday, October 24, 2013 2:15 AM
| To: c++std-ext_at_[hidden]
| Cc: WG21 UB study group; Xavier Leroy
| Subject: Re: [ub] [c++std-ext-14579] Re: Sized integer types and char bits
|
| On 10/23/13, Gabriel Dos Reis <gdr_at_[hidden]> 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.

Do you have specific optimizations in mind?

| As near as I can tell, the difference between the
| two terms does not affect programs trying for maximum portability.

That is my impressions.

-- Gaby


SG12 list run by herb.sutter at gmail.com