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 8558

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.
over 7 years ago in C/C++ and Fortran Compilers / C/C++ 2 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...
about 8 years ago in C/C++ and Fortran Compilers / C/C++ 3 Not under consideration

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...
over 8 years ago in C/C++ and Fortran Compilers / C/C++ 2 Future 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...
about 9 years ago in C/C++ and Fortran Compilers / Fortran 1 Not under consideration

87671, 49R, 000 BGQ , xlc++ 12.1.0.7 -O2 slow , vulcan , John Gyllenhaal

-------- Forwarded Message --------Subject: RE: 87671, 49R, 000 BGQ , xlc++ 12.1.0.7 -O2 slow , vulcan , John GyllenhaalDate: Wed, 21 Jan 2015 14:54:40 -0500From: Viktor Ganich <vganich@ca.ibm.com>To: Paul Szepietowski <pauls@llnl.gov>...
almost 10 years ago in C/C++ and Fortran Compilers / C/C++ 4 Not under consideration

Behaviour of comma operator in C++

We use multiple C and C++ compilers, including IBM XL C/C++ for AIX V11.1.0.18. XL C++ appears to treat comma expressions differently depending if they are an argument to a return statement or a function or if they are used elsewhere. This behavio...
over 10 years ago in C/C++ and Fortran Compilers / C/C++ 3 Not under consideration

Long compile time with -qsmp=omp for non-openmp files

XLC enforces -qhot optimization steps with -qsmp=omp option even for non-OMP source files, making the compile time unnecessarily long for such cases. The -qsmp=omp compile time issue becomes a dramatic problem because in user's makefile, the optio...
over 10 years ago in C/C++ and Fortran Compilers / C/C++ 6 Not under consideration

DB2 & CICS coprocessors do not provide enough debug information

To convert to co-processors we need to have the CICS and DB2 listings or something equivalent. We always print the first page of the DB2 and CICS pre-processor listingbecause they tell the applications the verson of DB2 the program was compiled us...
over 10 years ago in C/C++ and Fortran Compilers / C/C++ 4 Not under consideration

Provide some 64-bit compiler intrinsics when compiling 32-bit on a 64- bit architecture

The xlC compiler supplies (many) intrinsics that be used in lieu of assembly. Some of these intrinsic work on 32-bit words, and some on 64- bit double-words. (There are many others, but our interest here is 32- bit and 64-bit). __lwarx() load-word...
over 11 years ago in C/C++ and Fortran Compilers / C/C++ 8 Not under consideration

Erreur de compilation : No csects or exported symbols have been saved

Probl?me de compilation que nous rencontrons. C'est le dernier par rapport au lot que nous avons ? traiter.<br />L'erreur obtenue est la suivante :<br />ld: 0711-327 WARNING: Entry point not found: __start<br />ld: 0711-244 ERROR...
over 11 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.