On 01.04.22 17:11, Benedikt Freisen wrote:
The renaming was actually discussed rather extensively over the course
of about a year, albeit apparently only on the developer mailing list.
The actual renaming then took place in early December.
If you genuinely need the old target specific macros, yo
The renaming was actually discussed rather extensively over the course
of about a year, albeit apparently only on the developer mailing list.
The actual renaming then took place in early December.
If you genuinely need the old target specific macros, you could use a
compatibility header via pre-in
Hello Benedikt,
BF> Not only is sm83 the actual name of the CPU core in use, but
BF> additionally, multiple targets, including gbz80/sm83, got a new default
BF> calling convention with 4.2.0 that results in more efficient code.
Target name and calling conventions are VERY DIFFERENT, NOT CONNECTED
Hello Philipp,
Friday, April 1, 2022, 5:40:36 PM, you wrote:
ABI is another question. Marking functions as __sdcccall(0) is quite obvious
and very easy.
But renaming of target name lead to rewriting of TOOLS and MAKE SYSTEM of
GBDK-2020.
Also that will break building of pretty much projects,
Am 01.04.22 um 16:26 schrieb Tony Pavlov via Sdcc-user:
> Dear SDCC devs,
>
> can you please tell me, why target was renamed from gbz80 to sm83?
> who's brilliant idea? now we have to rework all gbdk-2020 build
> subsystem and that will definitely affect a lot of projects.
>
> WHAT FOR?!
>
There i
Am 01.04.22 um 16:26 schrieb Tony Pavlov via Sdcc-user:
Dear SDCC devs,
can you please tell me, why target was renamed from gbz80 to sm83?
who's brilliant idea? now we have to rework all gbdk-2020 build
subsystem and that will definitely affect a lot of projects.
WHAT FOR?!
Well, sm83 seeme
