https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78444
--- Comment #10 from Uroš Bizjak <ubizjak at gmail dot com> --- BTW: probably related to this PR, I have seen following kludge in i386/darwin.h: #define STACK_BOUNDARY \ ((profile_flag || TARGET_64BIT_MS_ABI) ? 128 : BITS_PER_WORD) It looks that profile_flag is there due to "call mcount" insn. However, crtl->profile is set in this case, and the vaule of the flag could be checked in the same place to eventually increase function alignment. Removing profile_flag would make Darwin's STACK_BOUNDARY definition the same as the default one, and could be removed.
