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]

Re: [Patch,AVR] Print no-return functions as JMP

From: Paolo Bonzini <bonzini at gnu dot org>
To: Georg-Johann Lay <avr at gjlay dot de>
Cc: Pedro Alves <pedro at codesourcery dot com>, gcc-patches at gcc dot gnu dot org, Richard Henderson <rth at redhat dot com>, Denis Chertykov <chertykov at gmail dot com>, Eric Weddington <eric dot weddington at atmel dot com>
Date: Sun, 16 Oct 2011 15:19:52 +0200
Subject: Re: [Patch,AVR] Print no-return functions as JMP
References: <4E972AEF.1020802@gjlay.de> <4E9867AA.3090909@gnu.org> <4E986F04.9090903@gjlay.de> <201110141955.18069.pedro@codesourcery.com> <4E99BB27.4090206@gjlay.de>

> -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

Follow-Ups:
- Re: [Patch,AVR] Print no-return functions as JMP
  - From: Georg-Johann Lay

References:
- [Patch,AVR] Print no-return functions as JMP
  - From: Georg-Johann Lay
- Re: [Patch,AVR] Print no-return functions as JMP
  - From: Paolo Bonzini
- Re: [Patch,AVR] Print no-return functions as JMP
  - From: Georg-Johann Lay
- Re: [Patch,AVR] Print no-return functions as JMP
  - From: Pedro Alves
- Re: [Patch,AVR] Print no-return functions as JMP
  - From: Georg-Johann Lay

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]