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 Future consideration
Categories z/TPF
Created by Guest
Created on Jun 7, 2023

(TPFUG/Visa) Utility required to identify code loaded to TPF that was built with a given compiler version or earlier

As part of compiler migration work we have to identify code loaded to TPF that was built with a version of the compiler that is no longer guaranteed to be compatible with a new compiler online execution environment. E.g. the GCC 7 execution environment will support code compiled with GCC 7 or GCC 4.6 but no guarantees are made for code built GCC 4.1 (or earlier, had there been an earlier compiler version supported on zTPF). If customers do not rebuild and load their entire code base as part of their compiler migration strategies, it is entirely possible that they have GCC 4.1 code still loaded. This code needs to be identified so it can be rebuilt and reloaded with the current compiler version before the new compiler execution environment is installed.


Currently, there is no easy way to identify code loaded to TPF that was built with a specific compiler version, or earlier. We have to rely on scans of listings for specific strings, or running readelf commands on SOs. Neither method accounts for the possibility that customer listing/SO locations on linux include code that is no longer actually loaded to TPF.

Ideally the new tooling would run on TPF to gather its information, so that we only gather information about code actually loaded to TPF.

Idea priority Medium