[DiscordArchive] Does this 1.12.1 have opcode list?
[DiscordArchive] Does this 1.12.1 have opcode list?
Original source
Does this 1.12.1 have opcode list?
rektbyfaith
12-03-2024, 09:55 AM #1Archived author: Deamon • Posted: 2024-12-03T09:55:25.298000+00:00
Original source
Does this 1.12.1 have opcode list?
Original source
As far as I remember opcode names were in 1.8.0 and then they disappeared until late BC or Wotlk. I do not remember for sure
rektbyfaith
12-03-2024, 09:56 AM #2Archived author: Deamon • Posted: 2024-12-03T09:56:54.355000+00:00
Original source
As far as I remember opcode names were in 1.8.0 and then they disappeared until late BC or Wotlk. I do not remember for sure
Original source
i am currently working on an archive which has pretty much all clients osx/win from 0.5.3.3368 to up and including 3.3.5.12340, and in multiple languages.
still processing (extracting, deduplicating) things... 10.4TB of data takes some time lol
will share it later, but will take some time
rektbyfaith
12-03-2024, 10:07 AM #3Archived author: 4bhorrent • Posted: 2024-12-03T10:07:00.663000+00:00
Original source
i am currently working on an archive which has pretty much all clients osx/win from 0.5.3.3368 to up and including 3.3.5.12340, and in multiple languages.
still processing (extracting, deduplicating) things... 10.4TB of data takes some time lol
will share it later, but will take some time
Original source
the approach for creating those client Installations was to install and patch all the way up from alpha (could be mistaken... there is a detailed spreadsheet on how the install path looked like).
the source is some guy over on the data mining discord, marlamin linked to it in the past.
the archive which is shared from there is 130GB and is heavily compressed + requires special software to use... just fyi ^^
if you want to do bulk processing/scanning, i would wait until i am done with my version of the archive though
rektbyfaith
12-03-2024, 10:11 AM #4Archived author: 4bhorrent • Posted: 2024-12-03T10:11:18.474000+00:00
Original source
the approach for creating those client Installations was to install and patch all the way up from alpha (could be mistaken... there is a detailed spreadsheet on how the install path looked like).
the source is some guy over on the data mining discord, marlamin linked to it in the past.
the archive which is shared from there is 130GB and is heavily compressed + requires special software to use... just fyi ^^
if you want to do bulk processing/scanning, i would wait until i am done with my version of the archive though
Original source
what the fuck, what did they do to unfatten those in 3.3.5
![[Image: image.png?ex=690c74c8&is=690b2348&hm=12e...84f2b0db6&]](https://cdn.discordapp.com/attachments/1086807686571642900/1313448009069101056/image.png?ex=690c74c8&is=690b2348&hm=12e92ee103108d948117272fcffbfd3ff5dab970682f1c9189fcbd784f2b0db6&)
rektbyfaith
12-03-2024, 10:13 AM #5Archived author: Aleist3r • Posted: 2024-12-03T10:13:28.104000+00:00
Original source
what the fuck, what did they do to unfatten those in 3.3.5
Original source
i will also ask the guy who made the archive for the patch sources, since he should have those as well
rektbyfaith
12-03-2024, 10:13 AM #6Archived author: 4bhorrent • Posted: 2024-12-03T10:13:48.749000+00:00
Original source
i will also ask the guy who made the archive for the patch sources, since he should have those as well
Original source
That sounds awesome. Looking forward to it!
rektbyfaith
12-03-2024, 11:23 AM #7Archived author: Deleted User • Posted: 2024-12-03T11:23:05.925000+00:00
Original source
That sounds awesome. Looking forward to it!
Original source
which version is that?
there are a lot of things one can do to slim down an exe:
cutting away debug symbols (only really valid for the osx ones)
getting rid of assertion strings
different encoding for stuff (compare utf8 and utf16, where the latter ALWAYS requires at least 2 bytes for a character).
dead code elemination (which i think should be hopefully rather small lol) and other more aggressive optimizations... can also go the other way with loop unrolling for example.
getting rid of obsolete resources like images etc which might be baked in.
different optimizations which allow SIMD instructions could cut down a lot of old scalar code, replacing it with a much smaller SIMD instruction list.
data alignment could have been changed to be more compact...
and certainly a lot of things i probably am forgetting rn ^^
rektbyfaith
12-03-2024, 11:33 AM #8Archived author: 4bhorrent • Posted: 2024-12-03T11:33:28.614000+00:00
Original source
which version is that?
there are a lot of things one can do to slim down an exe:
cutting away debug symbols (only really valid for the osx ones)
getting rid of assertion strings
different encoding for stuff (compare utf8 and utf16, where the latter ALWAYS requires at least 2 bytes for a character).
dead code elemination (which i think should be hopefully rather small lol) and other more aggressive optimizations... can also go the other way with loop unrolling for example.
getting rid of obsolete resources like images etc which might be baked in.
different optimizations which allow SIMD instructions could cut down a lot of old scalar code, replacing it with a much smaller SIMD instruction list.
data alignment could have been changed to be more compact...
and certainly a lot of things i probably am forgetting rn ^^
1 Guest(s)
1 Guest(s)