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 8224

Ship as PDSE for performance

With C header files in PDSes they cannot be cached in Z/OS and every compile needs to fetch from disk. If these were in PDSEs they they can be cached and avoid the I/O. See https://colinpaice.blog/2020/11/23/avoiding-i-o-by-caching-your-pdses-it-m...
almost 2 years ago in C/C++ and Fortran Compilers / z/OS 2 Not under consideration

Support for __ptr64 qualifier in LE C

LE C compiler should support the __ptr64 qualifier for 64-bit pointers in 31-bit (or 64-bit) code, as it does for Metal C. Furthermore, EDCDSECT should convert a 64-bit addresses (declared as "AD") to "void * __ptr64", for consistency.
almost 3 years ago in C/C++ and Fortran Compilers / C/C++ 2 Not under consideration

Port patch https://www.ibm.com/support/pages/apar/PI41717 from zOS for IBM i

Please port the patch https://www.ibm.com/support/pages/apar/PI41717 which is for zOS to IBM i, the same error exists in the sources of the IBM i hash function.
about 3 years ago in C/C++ and Fortran Compilers / C/C++ 5 Not under consideration

Provide I18N/L10N gettext APIs for XL/C on z/OS

A system level, common, industry standard, platform independent, service is needed to perform internationalization/localization translation services on text strings when running on z/OS. This is needed for both applications compiled to use Languag...
almost 6 years ago in C/C++ and Fortran Compilers / C/C++ 2 Not under consideration

Improve code generation for simple functions

Improve code generation for simple functions in METAL C: int func(const void* a, const void* b) { return memcmp(a,b,8); } in ILP32 mode the following code is generatedFUNC DS 0F STM 14,15,12(13) LR 15,13 L 13,8(,13) ST 15,4(,13) @@BGN@2 DS 0H USIN...
almost 6 years ago in C/C++ and Fortran Compilers / C/C++ 5 Not under consideration

Inline __asm() to communicate ARCHLVL to HLASM for system macros

When a z/OS system macro is embedded in a __asm() block, HLASM assumes ARCHLVL=1 which means the macro will use base+displacement branching, which fails in an inline __asm() block due to "no active USING". Most macros implement a MF=E form which g...
almost 6 years ago in C/C++ and Fortran Compilers / C/C++ 3 Not under consideration

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

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...
almost 8 years ago in C/C++ and Fortran Compilers / C/C++ 7 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.