Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Categories z/TPF
Created by Guest
Created on May 17, 2023

(TPFUG) Support generating a compiler warning if iostream is included in a build

With GCC 7, including iostream results in a global object being instantiated regardless of whether it is actually used. This drives substantial (approx 5% measured) overhead at runtime.  GCC 4.6 included a specific mod to defer instantiation until actual use, but the mod was not carried forward to GCC 7 and having to continuously carry forward a mod like this in future compiler versions is not ideal.

Given inclusion of iostream when not even needed has such an impact on runtime CPU, we would like the lab to enhance tooling to support generation of a compiler warning if iostream is used in a build. This will allow us to scrutinize all usage and remove all unnecessary calls. The support should probably be disabled by default but should be easily enabled if a customer wishes to use it. If enabled, the support would need to offer a means (e.g. a macro) of overriding the warning so that cases that truly need iostream can be compiled RC=0.

Idea priority High
  • Guest
    Reply
    |
    Jul 31, 2023
    This is available with z/TPF APAR PJ47102.