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: Is the loop pass allowed to introduce new call insns?

From: Richard Henderson <rth at redhat dot com>
To: John David Anglin <dave at hiauly1 dot hia dot nrc dot ca>
Cc: gcc at gcc dot gnu dot org
Date: Mon, 3 Mar 2003 16:55:36 -0800
Subject: Re: Is the loop pass allowed to introduce new call insns?
References: <20030303214642.GC12472@redhat.com> <200303032220.h23MKjsE015574@hiauly1.hia.nrc.ca>

On Mon, Mar 03, 2003 at 05:20:45PM -0500, John David Anglin wrote:
> Maybe I can stop this by adding "!virtuals_instantiated" to the
> condition for the various call expanders.

Nope.  That will only cause an abort at best.  One has to prevent
the call to expand_libcall_value.


r~

References:
- Re: Is the loop pass allowed to introduce new call insns?
  - From: Richard Henderson
- Re: Is the loop pass allowed to introduce new call insns?
  - From: John David Anglin

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