The way I handled things for inline assembly was to simply force use of
the old calling convention when being compiled with newer SDCC versions.
I simply define a faux function attribute depending on whether the
aforementioned __SDCCCALL define is present; if it is, 4.2.0+ is being
used, so fo
Am 10.09.22 um 20:44 schrieb Richard Hodges:
On 9/10/22 12:32 PM, Benedikt Freisen wrote:
Hi!
Silly question: Does anything speak against using the predefined
__SDCCCALL macro that -- if present -- specifies the ABI version?
Sorry, I accidentally replied to the sender and not the list.
I ju
On 9/10/22 12:32 PM, Benedikt Freisen wrote:
> Hi!
>
> Silly question: Does anything speak against using the predefined
> __SDCCCALL macro that -- if present -- specifies the ABI version?
>
Sorry, I accidentally replied to the sender and not the list.
I just tried this, and get an error:
sdcc
Hi!
Silly question: Does anything speak against using the predefined
__SDCCCALL macro that -- if present -- specifies the ABI version?
Am 10.09.22 um 20:06 schrieb Richard Hodges:
Hi, all.
I am finally getting to update my inline assembly for the new calling
version, started in 4.2 It is impor
