Jump to content

Recommended Posts

Hi,

   since using BoostC 8.01 I  have come across the message "Can't fit avoid code boundary code....". I have followed a couple of (Novo RTOS) posts about this (or similar) message and it seems that this incarnation of the compiler now builds a table (of return addresses?)for each call of a function. Because the table is only 256 entries long it effectively limits the number of times the function can be called (to 256).

Is my understanding correct so far?

256 calls may seem to be "a number unlikely to be exceeded" - but in my code and on bigger processors I use a lot of serial communication and my send_uart_char() , send_uart_str(), etc functions are used <a lot>.  

If this is a new limitation, then it is going to cause me a deal of pain with my existing libraries and programs - as a "pro user" I have to maintain these for a customer base....

Anyone else  experiencing this problem? Pavel, any comments on this? Could a compile switch be created to allow bigger call tables to be used?

 

Migration to Chameleon - ok, a possibility - but from what I have seen on the forum it is by no means "straightforward" - again this is going to cost me significant work time...

Edited by DTPIC
Link to post
Share on other sites

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...