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 Subscribe
Status Under review
Workspace C/C++ and Fortran Compilers
Categories AIX
Created by Guest
Created on Mar 12, 2024

RELATED IDEAS

redefining functions in header files - do it the right way

When functions in header files need to be redefined (e.g. to get new default behavior),
this should NOT be done by just renaming them with a simple '#define func_new func_old'.
Instead, macros should be used like it was done for older XL C/C++ compilers, for example:

    #pragma map(malloc,"vec_malloc")
    #pragma map(calloc,"vec_calloc")

or - as it was done for the newer compilers - with

    extern void *_NOTHROW(malloc, (size_t)) __asm__("vec_malloc");
    extern void *_NOTHROW(calloc, (size_t, size_t)) __asm__("vec_calloc");
 

But simply redefining (i.e. 'overwriting') a definition like it was done for the new default for LARGE_FILE support:

    #ifdef _LARGE_FILES
    #define stat    stat64
    #define fstat   fstat64

leads to all kind of trouble - and other plattforms also don't do it that way!

 

Regards,

Markus.

 

 

Idea priority High
  • Admin
    Basil Kanneth
    Reply
    |     Apr 8, 2024

    This Idea is being reviewed further.

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.