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 41

#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

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

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

Issue with Occurs clause Variables

We are migrating Micro focus COBOL programs to IBM COBOL for my client(shop direct). We see some initialization errors coming from mx20f program while compiling with IBM COBOL compiler. Initialization is not possible on occurs clause variables in ...
about 5 years ago in C/C++ and Fortran Compilers / C/C++ 4 Not under consideration

XLF: Compiler should detect and isolate the source of non-conforming Openmp code using local pointers for data maps.

SalesForce Case: TS001878905PMR: 80808,227,000 The use case reproducer for this issue is an OpenMP Fortran implementation that uses local, temporary pointers to do data mapping. The implementation does not conform to the OpenMP spec but the compil...
over 5 years ago in C/C++ and Fortran Compilers / Fortran 2 Not under consideration

XL: Support linking objects compiled with clang++ and xlc or xlf that use OpenMP GPU offloading

SalesForce Case TS001968579PMR 82483,227,000 XLF compiler: Errors linking objects compiled with clang++ and xlc or xlf that use OpenMP GPU offloading. LLNL is having problems linking objects that were compiled using the clang++ (LLVM) and XLF (or ...
over 5 years ago in C/C++ and Fortran Compilers / C/C++ 2 Not under consideration

RFE for header file cache optimization on C compiler

We would like to see the following implemented with the C compiler frontend just like it is for the C++ compiler frontend beginning with Xlc 12.1: -qxflag=dircache[,m[,n]] where m and n are optional * m is a integral prime number between 2 and 71 ...
about 11 years ago in C/C++ and Fortran Compilers / C/C++ 5 Not under consideration

XLF: request support for -shared flag consistent with the XLC usage

The XLC compiler accepts the "-shared" flag as an alias to "-qmkshrobj" to create shared object (.so) files, but the XLF compiler does not. The XLF option -shared is not documented but is not identified as invalid when it is used. Using -shared do...
almost 6 years ago in C/C++ and Fortran Compilers / Fortran 4 Not under consideration

Metal C - Compiler option to specify a register to map DSA

Currently Metal C uses Register 13 to map the DSA. Pls add a compiler option, for the user to specify the register that the compiler should use to map the DSA. Register 13 contents usually point to the save area. We have use cases, where the save ...
almost 6 years ago in C/C++ and Fortran Compilers / C/C++ 2 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.