{"push_id":1919261770,"size":1,"distinct_size":1,"ref":"refs/heads/hjl/pr81769/master","head":"7b69d6f8bc0de1b422f8b277c8d231f94b24efe6","before":"c7430dd4887a3ef5dca2009e2b9ee345f32fac51","commits":[{"sha":"7b69d6f8bc0de1b422f8b277c8d231f94b24efe6","author":{"name":"H.J. Lu","email":"2b186c3e9563c59778202d8011b384e4a9b5bbaf@gmail.com"},"message":"i386: Avoid stack realignment if possible\n\nix86_finalize_stack_frame_flags has been extended to eliminate frame\npointer when the new stack frame isn't needed with and without\n-maccumulate-outgoing-args as well as -fomit-frame-pointer.  Since stack\naccess with larger alignment may be optimized out, to decide if stack\nrealignment is needed, we need to not only check for stack frame access,\nbut also verify the alignment of stack frame access.  Since alignment of\nmemory access via arg_pointer is set up by caller, not by callee, we\nshould find the maximum stack alignment from the stack frame access\ninstructions via stack pointer and frame pointrer to avoid stack\nrealignment when stack alignment needed is less than incoming stack\nboundary.\n\ngcc/\n\n\tPR target/59501\n\tPR target/81624\n\tPR target/81769\n\t* config/i386/i386.c (ix86_finalize_stack_frame_flags): Don't\n\trealign stack if stack alignment needed is less than incoming\n\tstack boundary.\n\ngcc/testsuite/\n\n\tPR target/59501\n\tPR target/81624\n\tPR target/81769\n\t* gcc.target/i386/pr59501-4a.c: Remove xfail.\n\t* gcc.target/i386/pr81769-1a.c: New test.\n\t* gcc.target/i386/pr81769-1b.c: Likewise.\n\t* gcc.target/i386/pr81769-2.c: Likewise.","distinct":true,"url":"https://api.github.com/repos/gcc-mirror/gcc/commits/7b69d6f8bc0de1b422f8b277c8d231f94b24efe6"}]}
{"actor":{"display_login":"hubot"}}