Skip to Main Content
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.

Status Delivered
Categories C/C++
Created by Guest
Created on Jun 25, 2013

Add option to reduce error from severe to warning when using -qcheck compiler option

We'd like a way to be able to reduce a particular error from Severe to
a Warning so that compiles will proceed. SAS is interested in using the
XL C/C++ compiler option -qcheck=bounds; however, SAS has a lot of
legitimate legacy code that trips over this check causing compilations
to stop when a Severe error is reported. I've attempted to use the -
qhalt=u option and the -qnomaxerr options with thie -qcheck=bounds
option but the result is that compilation halts regardless and no
object file is produced.

See attached program s1298.c with further details:

xlc -c -qcheck s1298.c
"t.c", line 39.12: 1506-1298 (S) The subscript 3 is out of range. The
valid range is 0 to 1.

We'd like to make this a warning rather than a Severe error so that
compilations will proceed.

Idea priority High
  • Guest
    Reply
    |
    Sep 11, 2020

    XL C/C++ for AIX, V16.1 xlclang++ considers this as a warning instead of error. So we can go ahead and mark this RFE as complete:

    $ xlclang++ test.cpp -c
    test.cpp:9:7: warning: array index 3 is past the end of the array (which contains 2 elements) [-Warray-bounds]
    s->x[3] = 0;
    ^ ~
    test.cpp:3:7: note: array 'x' declared here
    int x[2];
    ^
    1 warning generated.
    $

  • Guest
    Reply
    |
    Sep 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - C/C++ Compilers

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - C/C++ Compilers

  • Guest
    Reply
    |
    Jan 2, 2014

    I'd like to see this RFE be addressed in an upcoming release of the compiler. Until this issue is addressed we can't use the -qcheck option. Most unfortunate.

  • Guest
    Reply
    |
    Oct 15, 2013

    This feature will be planned for a future release.

  • Guest
    Reply
    |
    Jun 25, 2013

    Attachment (Use case): Sample program that shows a problem with -qcheck compiler option that we are experiencing. We'd like the produced error to be a warning rather than severe so that compilation will continue.