• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 21 subscribers
  • Views 3189 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 Mark Odell

    To ensure vars. are placed in code memory you must define them with the code memory space qualifier. Your definition should absolutely be written as:

    static const float code ideal_values[LAST_POINT];


    This was one of the several incantations I tried, and I still get the warning. It was also suggested to make sure that variable was used in the function call, and it is. Another suggestion was to place this directly in the function that uses it (since the file only has one function in it, it is ONLY used by one function, and can go inside that function), but I haven't tried this yet.

    Anyone else have an idea?

Reply
  • 0 in reply to Mark Odell

    To ensure vars. are placed in code memory you must define them with the code memory space qualifier. Your definition should absolutely be written as:

    static const float code ideal_values[LAST_POINT];


    This was one of the several incantations I tried, and I still get the warning. It was also suggested to make sure that variable was used in the function call, and it is. Another suggestion was to place this directly in the function that uses it (since the file only has one function in it, it is ONLY used by one function, and can go inside that function), but I haven't tried this yet.

    Anyone else have an idea?

Children
No data