Timeline for Do the Windows shared source files compile into the same binaries as the retail version?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 16, 2014 at 10:31 | vote | accept | Peter Hahndorf | ||
| Sep 11, 2013 at 17:37 | comment | added | Steve | Sure, and that compilers won't necessarily output the same file byte-for-byte between builds. The real question is whether its possible to compare code paths to any reasonable certainty. | |
| Sep 11, 2013 at 7:27 | comment | added | Scott Chamberlain |
One big thing that will not be in ANY code sharing database will be the private keys to sign the files. Most of the "important" DLL's in windows (ntdll.dll, clfs.dll, ect...) are all digitally signed and there is no way to re-create that without the keys from Microsoft.
|
|
| Sep 10, 2013 at 18:39 | comment | added | Ramhound | If the rumors are correct Microsoft has replaced a great deal of those legacy components. They are able to do this because the kernel is actually getting smaller not larger. | |
| Sep 10, 2013 at 18:18 | history | edited | Steve | CC BY-SA 3.0 |
Removed potentially false assumption.
|
| Sep 10, 2013 at 18:15 | comment | added | Steve | A lot of the newer runtime components are C++ IIRC, but the core/kernel components are still C. The ratio I was told was around the post-Vista/pre-7 days. You're probably right about assembly though. My numbers are probably off. I'm going to edit it to clarify. | |
| Sep 10, 2013 at 14:30 | comment | added | Ramhound | Microsoft has actually moved away from C based on some rumors to a more traditional C++ code. Likewise the amount of assembly is also very limited which is pretty much only use to launch int the boot loader itself. | |
| Sep 9, 2013 at 15:13 | history | edited | Steve | CC BY-SA 3.0 |
updated explanation
|
| Sep 9, 2013 at 15:06 | history | answered | Steve | CC BY-SA 3.0 |