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 8228

Reliable indicator of AMODE in F7SA chain

When using Metal C, calling an ASCmode=AR function creates an ambiguous F7SA save area (in the DSA chain). The AMODE is switched BEFORE the call (BASR) is executed, and restored AFTER the return, so the AMODE of the caller (and therefore the DSAUS...
over 6 years ago in C/C++ and Fortran Compilers / C/C++ 2 Not under consideration

Document and support #pragma once in both C/C++

The z/OS C++ compiler supports the #pragma once directive. This is undocumented and not supported for the C language. This feature should be documented and supported for both the C and C++ languages.
almost 7 years ago in C/C++ and Fortran Compilers / C/C++ 2 Not under consideration

Exception Object Enhance

Exception handle is an important mechanism to help programmers debug their programs. Many of the literature books mention the use of this mechanism to increase the quality of the application. Although C11/C14 has no longer recommend the use of the...
about 7 years ago in C/C++ and Fortran Compilers / C/C++ 3 Not under consideration

#line directive causing source to not be intermixed in ASM listing

Sometimes C source code is embedded within generated pseudo assembly listings via the LIST option, like: 00012E 50D0 E004 000008 | ST r13,4(,r14)000132 18DE 000008 | LR r13,r14000134 End of Prolog 000009 | * { 000010 | * return foo();000134 58F0 3...
over 7 years ago in C/C++ and Fortran Compilers / C/C++ 3 Not under consideration

Add support to EDCDSECT for generating Doxygen-compatible comments

We have a product that has many data areas in common between C/C++ code and Assembler code. We generate the C/C++ header files from the Assembler DSECTs using the EDCDSECT utility provided by z/OS XL C/C++. We generate documentation for the C/C++ ...
almost 8 years ago in C/C++ and Fortran Compilers / C/C++ 21 Planned for future release

XL C/C++ compiler setting to disallow vector (VMX/VSX) instructions

Request for the compiler to support code generation consistent with an AIX tuning of allow_vmx=0. The AIX tuning rejects all vector instructions, treating them as illegal operations. The compiler should have a corresponding option to completely di...
almost 8 years ago in C/C++ and Fortran Compilers / C/C++ 2 Future 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...
about 8 years ago in C/C++ and Fortran Compilers / C/C++ 7 Not under consideration

FORTRAN V2.6 for z/OS - Add Compiler Option to Force Explicit Variable Declarations

The Fortran compiler for z/OS does not have a compiler option to force all variables to be explicitly declared. Instead each and every program has to be coded with an IMPLICIT NONE statement. We would like a compiler option to force this instead o...
over 8 years ago in C/C++ and Fortran Compilers / Fortran 1 Not under consideration

#pragma report should be extended to C

It is very frustrating that this pragma is not available in C, but only in C++!
almost 9 years ago in C/C++ and Fortran Compilers / C/C++ 4 Not under 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...
almost 9 years ago in C/C++ and Fortran Compilers / C/C++ 4 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.