This is the mail archive of the gcc@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: can_throw_internal affected by inlining?

From: Richard Henderson <rth at redhat dot com>
To: Jan Hubicka <hubicka at ucw dot cz>
Cc: jh at suse dot cz, gcc at gcc dot gnu dot org
Date: Sat, 11 Jul 2009 10:44:41 -0700
Subject: Re: can_throw_internal affected by inlining?
References: <4A57C772.7050509@redhat.com> <20090711125930.GB27815@atrey.karlin.mff.cuni.cz>

On 07/11/2009 05:59 AM, Jan Hubicka wrote:

Well, we can either teach inlinable_call_p to handle your new indirect
calls as "for sure uninlinable", make it conservative and consider all
calls inlinable or we can stop doing the early removal of MUST_NOT_THROW
receivers.

I think this last option would probably be best. Something to work on next week...

r~

Follow-Ups:
- Re: can_throw_internal affected by inlining?
  - From: Jan Hubicka

References:
- can_throw_internal affected by inlining?
  - From: Richard Henderson
- Re: can_throw_internal affected by inlining?
  - From: Jan Hubicka

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