https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78685
--- Comment #25 from jb at jeremybryant dot net --- Dear GCC Maintainers who have previously worked on bug 78685: Kindly note the bug below is still relevant for Emacs developers. (from the point of view of the C language compiler): Bug ID: 78685 Summary: -Og generates too many "<optimized out>"s Product: gcc Original report with sample code from Paul Eggert: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78685 >From the bug history there it appears that there was a potential patch solution by Tom de Vries, but apparently not applied: https://gcc.gnu.org/bugzilla/attachment.cgi?id=44343 And related work by Richard Sandiford who wrote RFC for rewriting -Og: https://gcc.gnu.org/legacy-ml/gcc-patches/2019-06/msg01394.html Referencing here a report on this general optimization topic, named "gOlogy" by Alexandre Oliva, of relevance to the general problem. aol...@redhat.com https://www.fsfla.org/~lxoliva/writeups/gOlogy/gOlogy.html The issue is still present in GCC 14.2. Would a solution be easier or different in the current version? Please accept my apology in case I have improperly followed conventions for following on this bug and do correct me if there is a better way to add this to the bug history. Furthermore please advise if there any testing that a general GCC user could do?
