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.

ADD A NEW IDEA

C/C++ and Fortran Compilers

Showing 51 of 8525

SASC/C++ Compiler Migration to XL C/C++

Below SASC/C++ functions are not available in XL C/C++ for RUV product. Could you please provide this functionality? S No. Function/ Parameters Description1 abort abnormally terminate execution2 access test for the existence and access privileges ...
almost 4 years ago in C/C++ and Fortran Compilers / C/C++ 3 Not under consideration

Raise a severe error if an unknown instruction is generated

If the Compiler/Optimizer generates an invalid unknown instruction (UNKWN), it have to raise a Severe Error. The assembly list shows unknown ?UNKWN? instructions: 000027 | ALRK r8,r7,r9 000027 | UNKWN r15,r3 000027 | UNKWN r8,r6 000027 | C r0,s.uw...
over 8 years ago in C/C++ and Fortran Compilers / C/C++ 7 Not under consideration

Add support for function inlining at OPT(0) [Metal C]

The METAL option of the xlc compiler does not support selectively inlining functions without optimizing the rest of the code We would like to be able to use a compiler attribute (such as "__always_inline__" or "_inline") to force inlining of certa...
over 4 years ago in C/C++ and Fortran Compilers / C/C++ 2 Not under consideration

XL Fortran Bogus Error on Assumed Shape Dummy Argument of BIND(C) Procedure

The XL Fortran compiler gives a bogus error message for the below valid Fortran program. The restriction that presumably generates this error message was replaced in Fortran 2018 standard (sec 18.3.6 point 5). Furthermore, the XL compiler provides...
over 4 years ago in C/C++ and Fortran Compilers / Fortran 1 Future consideration

#pragma report should be extended to C

It is very frustrating that this pragma is not available in C, but only in C++!
over 9 years ago in C/C++ and Fortran Compilers / C/C++ 4 Not under consideration

XL C/C++ for z/OS Compiler Features

We'd like to move to using the newer Clang-based XL C/C++ compiler, but we need some features that are not present in the newer product, namely: AMODE31 supportEBCDIC supportHex float support
over 4 years ago in C/C++ and Fortran Compilers / C/C++ 2 Future consideration

Perform optimizations based on __attribute__((__malloc__))

Currently, __attribute__((__malloc__)) does not work as documented in the compiler docs. The documentation infers that the compiler performs certain optimizations when using __malloc__ attribute. However, it appears that the compiler simply tolera...
over 9 years ago in C/C++ and Fortran Compilers / C/C++ 4 Not under consideration

The C++ interface for demangling new cxxabi names(generated by xlclang 16.1) are not implemented.

The C++ interface for demangling new cxxabi names(generated by xlclang 16.1) are not implemented. The C++ interface could only demangle old C++ names generated by xlC.
almost 5 years ago in C/C++ and Fortran Compilers / C/C++ 1 Future consideration

Using CPACF with HW built-In instructions

ISV likes to use HW Crypto support of CPACF (see Principles of Operation) in their applications running on z/OS. As of requiremts of their architecture and as of performance reasons, they do not use ICSF. So they have to use the CPACF instructions...
almost 10 years ago in C/C++ and Fortran Compilers / C/C++ 7 Not under consideration

Provide Fortran compiler option to force variables to be explicitly declared

The IMPLICIT none statement is available to us, but it has to be coded in every single program, subroutine and function, whereas a compiler option would not require a code modification to enforce explicit declarations. The PL/I compiler has the RU...
about 10 years ago in C/C++ and Fortran Compilers / Fortran 3 Not under consideration

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.