From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: rth@redhat.com (Richard Henderson)
Cc: gcc@gcc.gnu.org
Subject: Re: Is the loop pass allowed to introduce new call insns?
Date: Mon, 03 Mar 2003 23:12:00 -0000 [thread overview]
Message-ID: <200303032220.h23MKjsE015574@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <20030303214642.GC12472@redhat.com> from "Richard Henderson" at Mar 3, 2003 01:46:42 pm
> Not sure what to do about this...
Maybe I can stop this by adding "!virtuals_instantiated" to the
condition for the various call expanders.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
next prev parent reply other threads:[~2003-03-03 22:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 20:51 John David Anglin
2003-03-03 22:20 ` Richard Henderson
2003-03-03 23:12 ` John David Anglin [this message]
2003-03-04 1:03 ` Richard Henderson
2003-03-04 0:20 ` law
2003-03-04 0:55 ` John David Anglin
2003-03-04 1:22 ` Richard Henderson
2003-03-04 5:29 ` John David Anglin
2003-03-04 7:40 ` Richard Henderson
2003-03-04 8:35 ` John David Anglin
2003-03-06 16:15 ` law
2003-03-09 20:17 ` [PATCH]: " John David Anglin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200303032220.h23MKjsE015574@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).