{"push_id":1479234297,"size":2,"distinct_size":1,"ref":"refs/heads/master","head":"16e5869f82d457833ef0fc6ebd70334a80b43c32","before":"5c6b699b366d1e27be33d3ea97cf70e15bd1c4ae","commits":[{"sha":"be6568111d709ac1c64fb70aeecf1ffc4a217c9a","author":{"name":"hMihaiDavid","email":"ac823b8fdfdda54f16195a9d350f54c681b30326@gmail.com"},"message":"flush instruction cache after performing relocations\n\nFlush instruction cache to avoid executing stale code after performing relocations.\r\nAccording to MSDN: \"Applications should call FlushInstructionCache if they generate or modify code in memory. The CPU cannot detect the change, and may execute the old code it cached.\".\r\nAfter performing relocation we have modified executable code, so if we don't flush the cache maybe the old code without relocation is executed instead. So far the code has woked without flushing instruction cache but it's better to be safe.\r\n\r\nhttps://msdn.microsoft.com/en-us/library/windows/desktop/ms679350(v=vs.85).aspx","distinct":false,"url":"https://api.github.com/repos/hMihaiDavid/MemoryModule/commits/be6568111d709ac1c64fb70aeecf1ffc4a217c9a"},{"sha":"16e5869f82d457833ef0fc6ebd70334a80b43c32","author":{"name":"hMihaiDavid","email":"ac823b8fdfdda54f16195a9d350f54c681b30326@gmail.com"},"message":"Merge pull request #1 from hMihaiDavid/hMihaiDavid-patch-1\n\nflush instruction cache after performing relocations","distinct":true,"url":"https://api.github.com/repos/hMihaiDavid/MemoryModule/commits/16e5869f82d457833ef0fc6ebd70334a80b43c32"}]}
{"actor":{"display_login":"hMihaiDavid"}}