PkK Posted June 12, 2016 Share Posted June 12, 2016 Since a few hours, there is SDCC 3.6.0: Today a new release of SDCC was made. We are now at version 3.6.0.You can get it at:http://sourceforge.net/projects/sdcc/files/So what's new?* Merged upstream binutils 2.25* New memory management with lower overhead* Changed default language dialect to --std-sdcc11* Diagnostic for missing type specifier: No implicit int outside of C90mode anymore* C11 generic selections* char type is now unsigned by default (old behaviour can be restoredusing --fsigned-char)* Character constants are now of type int instead of char.* ISO C95 and ISO C11 wide character constants* ISO C95 and ISO C11 wide string literals* Basic standard library support for wide characters: c16rtomb(),mbrtoc16(), mbsinit(), mbtowc(), mbrlen(), mbrtoc32, c32rtomb(),mbrtowc(), wcrtomb(), mblen(), wctomb()* Treat all ports the same in the manual (i.e. mcs51-specific stuff is nowclearly described as such)* Reorganized interrupt handling for z80, z180, r2k, r3ka, tlcs90, gbz80backends* Workaround for stm8 division hardware bug* ELF/DWARF support for stm8* Output symbol table for ELF* pic16 port now uses standard-compliant crt0iz that initializes staticand globals to 0 by defaultAnd of course numerous feature requests and bug fixes are included as well.Once again I hope you will enjoy using this new release.Maarten BrockSDCC 3.6.0 Release Manager Most relevant for ColecoVision programmers are probably the improved standard support and various bugfixes in the Z80 backend. Philipp 1 Quote Link to comment Share on other sites More sharing options...
digress Posted June 13, 2016 Share Posted June 13, 2016 upgraded. Thanks for the notice. Tested it with my current project and after a bit of reworking it all works fine. Main thing I ran into was I was using signed characters -48,-36 etc. SO I converted them all to unsigned 0 -255 and it's all good so far. smooth transition other wise Not sure yet but it might have even removed a graphic glitch I was having. Might be just a coincidence. Hasn't shown up today anyways. Quote Link to comment Share on other sites More sharing options...
PkK Posted June 15, 2016 Author Share Posted June 15, 2016 At FOSDEM 2015, there was a talk on SDCC: https://archive.fosdem.org/2015/schedule/event/8bit_compiler/ there is also a blog post on what happened in SDCC since the talk up to the SDCC 3.6.0 release: http://www.embecosm.com/2016/06/14/recent-updates-to-sdcc-in-release-3-6-0/ Philipp Quote Link to comment Share on other sites More sharing options...
alekmaul Posted July 3, 2016 Share Posted July 3, 2016 (edited) hum, it seems that rom compiled with new version take more space than with sdcc3.5 :/ Do we need to use special option to have same optimization like for sdcc 3.5 ? Area Addr Size Decimal Bytes (Attributes)-------------------------------- ---- ---- ------- ----- ------------_CODE 00008048 00007F58 = 32600. bytes (REL,CON) with sdcc 3.5 and with sdcc 3.6 I have 87 bytes more :/ Compilation option for 3.5 : CFLAGS += -mz80 -c -I$(CVLIB)/include -I$(DEVKITSDCC)/include --std-sdcc99 -O3 --vc and for 3.6 : CFLAGS += -mz80 -c -I$(CVLIB)/include -I$(DEVKITSDCC)/include O3 --vc Edited July 3, 2016 by alekmaul Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. 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.