![]() Therefore we decided to make a difference in optimizations between the two available builds of DC++: the 64-bit build, named “Optimized” from now, will require a CPU that is manufactured in the last 10 years going forward whereas we plan to make the 32-bit build (now called “Legacy”) remain usable on pretty old (currently 15+ year old) computers and 32-bit client editions of Windows. At the same time, if we decide to require at most ~10 year old CPUs now then we can go much further with optimizations as there are plenty of other new CPU opcodes are supported by the processors that has been manufactured in this timeframe. Aging of PCs are knowlingly slowed down in the recent years so requiring this feature would make the latest versions of DC++ unusable on many old but still working PCs and we’d like to avoid that. The obvious step forward is to require SSSE3 to gain more advantages but there’s a caveat: while Intel introduced this feature in its client CPUs in 2006, AMD has added it only surprisingly later, in 2011. We added those optimizations carefully back then, knowing all the features in case had been already widely introduced in all CPUs manufactured in the previous 10 years or more so it shouldn’t have caused issues for the vast majority of users who care to keep their system and software up to date. They have brought siginificant advantages and optimizations to the code as you see in the linked posts in detail. ![]() ![]() We already require SSE3 since DC++ version 0.863 and SSE2 since 0.861. DC++ has already introduced CPU opcode feature requirements in the past when those features were widespread enough in various PC hardware the program had been used on. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |