• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 21 subscribers
  • Views 3222 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

cannot figure out this link warning

J Nelson Chadderdon

I am using 5.20 if it matters

I have a function that is indirectly called from an array of functions. This function is contained in its own module. When I link, I get the following warning:

WARNING 16: Uncalled Segment, ignored for overlay process
segment: ?CO?FACT_CON

in this module I have one variable that I define as

static float code ideal_values[LAST_POINT] ={

if I change the "code" to "const" (or remove it entirely), it will link with no warnings, but now the variable is taking up XDATA, and with only 2K of it, XDATA is VERY precious...

I've also tried several other incantations of the same line of code. It either ends up in XDATA, or gives me the warning.

I've had this problem in several other places, but until now, I chosen to ignore it... any ideas? (if anyone thinks more info is needed, please ask, I just didn't want to flood the list with things like link maps, and other such things)

Parents
  • 0 in reply to J Nelson Chadderdon

    This is just a suggestion.

    I declare an array of function pointers to solve similar problem in my current project. It works without warning, the array is placed in code memory, and the overlay analysis is used for the whole project.

    You could try this:

    static const float (code* code ideal_value[LAST_POINT])(void) = {fnct1, fnct2};

    This simply declare an array of pointers to functions that return float and take no argument. The array is placed in the code.

    Invoke the function by:
    x = ideal_value[i]();
    or
    x = (*ideal_value[i])();

    I hope this solve your problem.

    David Lin

Reply
  • 0 in reply to J Nelson Chadderdon

    This is just a suggestion.

    I declare an array of function pointers to solve similar problem in my current project. It works without warning, the array is placed in code memory, and the overlay analysis is used for the whole project.

    You could try this:

    static const float (code* code ideal_value[LAST_POINT])(void) = {fnct1, fnct2};

    This simply declare an array of pointers to functions that return float and take no argument. The array is placed in the code.

    Invoke the function by:
    x = ideal_value[i]();
    or
    x = (*ideal_value[i])();

    I hope this solve your problem.

    David Lin

Children
No data