So before you accuse, first read the ff'ing docs, like here or here or. So back to testing, research the optimization options test with -s and examine the output.ītw: first checkout the docs on CSE. Because the output needs to run on a worse case specced computer too. Sv)Ī generic compiler usually optimizes worse case specified. If you want AVX code for example, you will need to specify that. You have to specify the desired optimizations, although -O4 will turn most, but not all of them on. sort_year := wait^^.date.dyear įPC is just conservative in its default settings. The code generated for this, enabling all optimizations in the IDE makes me very sad, as it's hardly better than what Turbo Pascal used to generate more than three decades ago! Obviously I don't expect it the code to come anywhere close to manually optimized code, but this code generated doesn't even try:Ĭode: sort_wptr := wait^ My benchmark is a routine that does a Shellsort on an array of pointers, comparing two variables in the list items the pointers point to. So let's just look a bit at the generated code. However, it ABENDs (z/OS parlance for crash) in "readfile" with Very, very,very obviously my version of LIFT (in lift32bit.rar) that's nearly fully recoded into inline assembler does not compile, but after changing eight definitions of variables in hhcommon.pas from longint to word (for the DOS GetTime function), the "Pure Pascal" version compiles without problems. So I installed FPC again, for yet another try, as I'm getting a bit tired of DB coding MMX/SSE/AVX instructions in Virtual Pascal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |