{"push_id":2471062638,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"0ea26847d969338cd7d1e27f15a2da3691ab192f","before":"3b3740ba8ac23f698cf25aedb141696eaf82311a","commits":[{"sha":"0ea26847d969338cd7d1e27f15a2da3691ab192f","author":{"name":"Chandler Carruth","email":"420c9fb3407b8e11ac322a0e7703f7b1f526df04@gmail.com"},"message":"[x86] Model the direction flag (DF) separately from the rest of EFLAGS.\n\nThis cleans up a number of operations that only claimed te use EFLAGS\ndue to using DF. But no instructions which we think of us setting EFLAGS\nactually modify DF (other than things like popf) and so this needlessly\ncreates uses of EFLAGS that aren't really there.\n\nIn fact, DF is so restrictive it is pretty easy to model. Only STD, CLD,\nand the whole-flags writes (WRFLAGS and POPF) need to model this.\n\nI've also somewhat cleaned up some of the flag management instruction\ndefinitions to be in the correct .td file.\n\nAdding this extra register also uncovered a failure to use the correct\ndatatype to hold X86 registers, and I've corrected that as necessary\nhere.\n\nDifferential Revision: https://reviews.llvm.org/D45154\n\nllvm-svn=329673","distinct":true,"url":"https://api.github.com/repos/jyknight/llvm-monorepo/commits/0ea26847d969338cd7d1e27f15a2da3691ab192f"}]}
{"actor":{"display_login":"jyknight"}}