This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
-moptimize-noreturn-calls Optimize noreturn calls. This might make debugging harder but will save storing the return address when calling roreturn functions.
Enabled at levels -O2, -O3, -Os.
But the "makes debugging harder" clause is true for almost any optimization available, so should this tautology be mentioned along with each optimization that makes debugging harder?
If there's one kind of debugging that you don't want to make harder, that's post mortem debugging.
Paolo
- Not to imlement this optimization at all? - Implement it but don't turn it on depending on -O* - Implement it as is but explicitely mention "post mortem debugging" in docs?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |