i guess that a problem is the semantics of CODE/FAR/NEAR is not very well documented.
On Thu, Jan 27, 2022 at 5:21 AM Gregory Nutt <spudan...@gmail.com> wrote: > > > > >> Should be nice if we could find a wait to instruct the compiler (or > >> the building system) to include the typedefed CODE to the pointer > >> functions automatically, but I don't know if it is possible. > >> > >> I think you are all making risky irresponsible changes to fix something > > that is not broken. > > > > Also, I don't think that you can assume that a pointed-at function resides > in code ROM. Couldn't it also reside in RAM? I could imagine having FAR > function pointers and CODE function pointers and we should not limit the > support. do you mean they would be "void (CODE *f)(void)" and "void (FAR *f)(void)" respectively?
