https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118939
--- Comment #20 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > If the value returned is different from earlier, then it has changed. Using > different methods for calculating the size during different passes would a > recipe for endless bugs, especially if crufted into the back-ends. get_frame_size has always worked like this and rewriting it is not the point of this discussion I think. > The mid-end code has to cope with that. There may be circumstances where we > initially think the frame-pointer can be eliminated, but later find we > can't. It won't flip-flop randomly, but it might have to change based on > additional knowledge that is aquired as the frame layout process is done. The point is not the flip-flop per se, but the timing of the last flop, which is now much later that it used to before the aforementioned change.
