Skip to main content
Redhat Developers  Logo
  • Products

    Featured

    • Red Hat Enterprise Linux
      Red Hat Enterprise Linux Icon
    • Red Hat OpenShift AI
      Red Hat OpenShift AI
    • Red Hat Enterprise Linux AI
      Linux icon inside of a brain
    • Image mode for Red Hat Enterprise Linux
      RHEL image mode
    • Red Hat OpenShift
      Openshift icon
    • Red Hat Ansible Automation Platform
      Ansible icon
    • Red Hat Developer Hub
      Developer Hub
    • View All Red Hat Products
    • Linux

      • Red Hat Enterprise Linux
      • Image mode for Red Hat Enterprise Linux
      • Red Hat Universal Base Images (UBI)
    • Java runtimes & frameworks

      • JBoss Enterprise Application Platform
      • Red Hat build of OpenJDK
    • Kubernetes

      • Red Hat OpenShift
      • Microsoft Azure Red Hat OpenShift
      • Red Hat OpenShift Virtualization
      • Red Hat OpenShift Lightspeed
    • Integration & App Connectivity

      • Red Hat Build of Apache Camel
      • Red Hat Service Interconnect
      • Red Hat Connectivity Link
    • AI/ML

      • Red Hat OpenShift AI
      • Red Hat Enterprise Linux AI
    • Automation

      • Red Hat Ansible Automation Platform
      • Red Hat Ansible Lightspeed
    • Developer tools

      • Red Hat Trusted Software Supply Chain
      • Podman Desktop
      • Red Hat OpenShift Dev Spaces
    • Developer Sandbox

      Developer Sandbox
      Try Red Hat products and technologies without setup or configuration fees for 30 days with this shared Openshift and Kubernetes cluster.
    • Try at no cost
  • Technologies

    Featured

    • AI/ML
      AI/ML Icon
    • Linux
      Linux Icon
    • Kubernetes
      Cloud icon
    • Automation
      Automation Icon showing arrows moving in a circle around a gear
    • View All Technologies
    • Programming Languages & Frameworks

      • Java
      • Python
      • JavaScript
    • System Design & Architecture

      • Red Hat architecture and design patterns
      • Microservices
      • Event-Driven Architecture
      • Databases
    • Developer Productivity

      • Developer productivity
      • Developer Tools
      • GitOps
    • Secure Development & Architectures

      • Security
      • Secure coding
    • Platform Engineering

      • DevOps
      • DevSecOps
      • Ansible automation for applications and services
    • Automated Data Processing

      • AI/ML
      • Data Science
      • Apache Kafka on Kubernetes
      • View All Technologies
    • Start exploring in the Developer Sandbox for free

      sandbox graphic
      Try Red Hat's products and technologies without setup or configuration.
    • Try at no cost
  • Learn

    Featured

    • Kubernetes & Cloud Native
      Openshift icon
    • Linux
      Rhel icon
    • Automation
      Ansible cloud icon
    • Java
      Java icon
    • AI/ML
      AI/ML Icon
    • View All Learning Resources

    E-Books

    • GitOps Cookbook
    • Podman in Action
    • Kubernetes Operators
    • The Path to GitOps
    • View All E-books

    Cheat Sheets

    • Linux Commands
    • Bash Commands
    • Git
    • systemd Commands
    • View All Cheat Sheets

    Documentation

    • API Catalog
    • Product Documentation
    • Legacy Documentation
    • Red Hat Learning

      Learning image
      Boost your technical skills to expert-level with the help of interactive lessons offered by various Red Hat Learning programs.
    • Explore Red Hat Learning
  • Developer Sandbox

    Developer Sandbox

    • Access Red Hat’s products and technologies without setup or configuration, and start developing quicker than ever before with our new, no-cost sandbox environments.
    • Explore Developer Sandbox

    Featured Developer Sandbox activities

    • Get started with your Developer Sandbox
    • OpenShift virtualization and application modernization using the Developer Sandbox
    • Explore all Developer Sandbox activities

    Ready to start developing apps?

    • Try at no cost
  • Blog
  • Events
  • Videos

Red Hat at the ISO C++ Standards Meeting (February 2014)

May 28, 2014
Matt Newsome
Related topics:
Developer ToolsLinux
Related products:
Developer ToolsRed Hat Enterprise Linux

Share:

    Red Hat has actively participated in the ISO group defining the C++ standard for many years, and continues to make a significant contribution. The Red Hat toolchain team was well-represented at the February 2014 meeting of the standardization committee (JTC1/SC22/WG21) in Issaquah, WA, USA. In this article, Jason Merrill summarizes the main highlights and developments of interest to Red Hat's customers and partners:

    In February, Red Hat sent three engineers to the C++ standards committee meeting in Issaquah, WA.  The committee had dealt with most of the national body comments on the post-Bristol Committee Draft of C++14 at the previous meeting in Chicago, so this meeting was largely about putting the finishing touches on and addressing a few more National Body comments.

    As usual, Red Hat was represented in the Core Language working group, the Evolution working group (notably supporting review of the Concepts Lite paper since the proposal is being developed together with the GCC implementation) and the Library working group, among others.  Since we spent the Chicago meeting processing National Body comments, we had a backlog of normal issues to get through; we reviewed a lot of proposed resolutions at the meeting, of which I provided drafting for 20 issues.

    Several of the issues we were looking at were relevant to optimization:

    • One of them was my drafting for issue 1338, clarifying that the optimizer is allowed to treat ::operator new (size_t) like malloc, and assume the return value can't alias anything.  Other GCC folks have been asking for this for a while.
    • Another was 1766, which made converting a value outside the range of values of an enumeration undefined behavior.  This basically reverses the earlier resolution of issue 1094, which I had raised in response to GCC BZ c++/42810 (optimizing away loop exit tests with enums).  I see no need to change the compiler to match, but it seems that other compilers do and will continue to optimize that way, so this will be important to check with gcc's Undefined Behavior Sanitizer (ubsan).
    • 1776 has to do with the language in 3.8 specifying that if an object (or subobject) is created with a const or reference type, a compiler is allowed to assume that its value never changes.  This is problematic for the optional<T> class in the Library Fundamentals Technical Specification, which wants to be able to destroy its subobject and then construct a new one in its place, which leads to undefined behavior if T happens to have a const or reference field.  Core decided to deal with this by passing the pointer through a function (tentatively named "launder") to break its association with any knowledge about an object; optional<T> will need to use that whenever returning a pointer to its subobject.
    • We also dealt with some refinement of the C++14 permission for the compiler to combine multiple new/delete pairs into a single allocation, or even to replace them with stack allocation.  A Google representative was saying that this is very beneficial for functions with a bunch of std::strings as local variables.

    Getting away from optimization issues, we also reviewed my drafting to allow deduction of an array type from a C++11 brace-enclosed initializer list.

    We've been changing handling of an initializer list with a single element to be just expressing direct-initialization from that element when that makes sense.  In response to a National Body comment from Finland, it looks like we're going to drop deduction of std::initializer_list for C++11 'auto' in the case where there is no '=' in the initializer clause, i.e.

    auto x { 42 };

    will now deduce 'int' rather than 'std::initializer_list<int>'.

    We keep refining the specification of reference binding in 8.5.3; hopefully my latest drafting actually expresses what we want it to.

    We seem to be backing off uniqueness of string literals in inline functions, because it wasn't widely implemented.

    At the end of the week, voting went very smoothly; Red Hat was actually the only organization that raised any discussion of the motions.  We abstained from a couple of the motions because they call for modifying the ABI of existing standard library classes in a Technical Specification, which seems inappropriate. I expect that this will be fixed at the meeting in June.

    Thanks to Jason Merrill of Red Hat's toolchain team for this summary.

    Recent Posts

    • Ollama or vLLM? How to choose the right LLM serving tool for your use case

    • How to build a Model-as-a-Service platform

    • How Quarkus works with OpenTelemetry on OpenShift

    • Our top 10 articles of 2025 (so far)

    • The benefits of auto-merging GitHub and GitLab repositories

    Red Hat Developers logo LinkedIn YouTube Twitter Facebook

    Products

    • Red Hat Enterprise Linux
    • Red Hat OpenShift
    • Red Hat Ansible Automation Platform

    Build

    • Developer Sandbox
    • Developer Tools
    • Interactive Tutorials
    • API Catalog

    Quicklinks

    • Learning Resources
    • E-books
    • Cheat Sheets
    • Blog
    • Events
    • Newsletter

    Communicate

    • About us
    • Contact sales
    • Find a partner
    • Report a website issue
    • Site Status Dashboard
    • Report a security problem

    RED HAT DEVELOPER

    Build here. Go anywhere.

    We serve the builders. The problem solvers who create careers with code.

    Join us if you’re a developer, software engineer, web designer, front-end designer, UX designer, computer scientist, architect, tester, product manager, project manager or team lead.

    Sign me up

    Red Hat legal and privacy links

    • About Red Hat
    • Jobs
    • Events
    • Locations
    • Contact Red Hat
    • Red Hat Blog
    • Inclusion at Red Hat
    • Cool Stuff Store
    • Red Hat Summit
    © 2025 Red Hat

    Red Hat legal and privacy links

    • Privacy statement
    • Terms of use
    • All policies and guidelines
    • Digital accessibility

    Report a website issue