Upcoming vbcc 0.9h release
You know I hate such announcements, to keep the pressure away from our
developments, but we really would like to do the next vbcc release during the following weeks. As those stable releases only happen every two years on average, I would like to give you a last opportunity to report important bugs or feature requests, for vbcc, vasm and vlink. Although feature requests may be postponed, if they would delay the release too much. Please contact me by email! You find it on the bottom of the vbcc release page: http://sun.hasenbraten.de/vbcc/ I might also publish a link to the current beta version during this weekend, so you can check if your bugs are already gone. We worked hard, especially during this year, to fix so many bugs and improve the code generator quality noticeably - both in code size and speed. Here is a totally incomplete and mostly unsorted list: Code:
- improved function inlining |
Ok, here are the promised links for the beta. I had to delay it, because I was hunting a bug over the last days which turned out being a known 68060 errata in the end.
Some binaries: http://sun.hasenbraten.de/~frank/TEST/vbcc_bin_amigaos68k.lha http://sun.hasenbraten.de/~frank/TEST/vbcc_bin_amigaosppc.lha http://sun.hasenbraten.de/~frank/TEST/vbcc_bin_morphos.lha Some targets: http://sun.hasenbraten.de/~frank/TEST/vbcc_target_m68k-amigaos.lha http://sun.hasenbraten.de/~frank/TEST/vbcc_target_m68k-kick13.lha |
Do you have source available?
I'd like to test some fixes and look for regressions. My projects are cross-compiled from Linux. I haven't got a 68K toolchain set up. |
Quote:
If you can't wait, just write me a mail and you get it. |
Here is the latest vbcc source. Last change was 18th of December. It's the same which was used to build the Amiga binaries:
http://sun.hasenbraten.de/~frank/TEST/vbcc.tar.gz |
Sorry, never came around to test on Linux with target WarpOS anymore. How much time till release?
|
Quote:
A few weeks at least... |
I've confirmed the two bugs I reported in 0.9g are fixed.
The volatile optimization fix is really helpful. I was tripping all over that in hardware banging code. :) |
Ooh, I missed this until yesterday. I built for Mac yesterday, and have not noticed any changes so far in my limited "testing". Everything seems to just "work", using the updated 68K target.
|
Thanks to all the testers!
It's just "two more weeks"... ;) |
I think there still might be an issue regarding volatile memory accesses when doing them through a struct pointer.
Condensed test case: Code:
struct Custom { vbccm68k -O=179 test.c(seems to be minimal flags necessary). Compiling With -O=163 crashes the compiler. Note: I built the compiler myself, so that might be an issue (just accepted defaults when doing make TARGET=m68k), tried both windows and linux. Stacktrace for crash is: Code:
#0 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:319 |
Indeed! I can confirm both issues, even with the latest beta. Thanks for reporting. Will be fixed immediately.
|
Fixed. The latest beta source is here:
http://sun.hasenbraten.de/~frank/TEST/vbcc.tar.gz The crash with -O=163 was not fixed, because this is an illegal combination of optimizer flags, and Volker wants to keep it for testing. |
Confirmed, thanks. Regarding -O=163 that's totally fine, it was just something I noticed while trying to minimize the number of flags for the bug report (I've just been compiling using vc -O2), I weren't actually checking what they were doing / made sense in combination. Also sounds good with the __gmtoffset change!
|
Release
Released!
http://sun.hasenbraten.de/vbcc/ |
Thanks for all the hard work you guys put into it, and congrats on the release. One note: It seems like the win64 binaries haven't been updated (they say "vbcc V0.9h pre (c) in 1995-2020"). Was just about to post a real bug report until I noticed this :)
EDIT: Actually I see the same issue for the AmigaOS ones |
Dear PHX and all VBCC developers: congrats thank you! :great
Going to install it very soon! :) Cheers! |
To phx and the VBCC developers: thank you for your continued support of the Amiga community.
|
Quote:
I made a mistake while packing the archive, and I have no easy way to test Windows binaries. Reuploaded the (hopefully) recent binaries now. |
Quote:
Thanks, yes, now it works as expected. However I still have an issue with the AmigaOS 2.x/3.x 68020+ binaries.Shouldn't they generate the same code as the (updated) win64 version when using the same compiler flags? The code worked with the 0.9g release and also when compiled with 0.9h on windows. EDIT: Code:
void foo(void) Wit the amiga OS version I get a loop that looks like this: Code:
moveq #8,d2 Code:
moveq #8,d3 |
All times are GMT +2. The time now is 05:06. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.