public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Andreas Bauer <baueran@in.tum.de>
Cc: gcc-patches@gcc.gnu.org, pizka@informatik.tu-muenchen.de,
	jason.ozolins@anu.edu.au
Subject: Re: PATCH for sibcalls on i386
Date: Mon, 23 Sep 2002 15:12:00 -0000	[thread overview]
Message-ID: <20020923181211.K20637@redhat.com> (raw)
In-Reply-To: <20020923141054.B26514@royal.anu.edu.au>; from baueran@in.tum.de on Mon, Sep 23, 2002 at 02:10:54PM +1000

I'll only comment on the md change, since Fergus and Zack
have adequately addressed the generic change that the proper
way to attack this problem.

On Mon, Sep 23, 2002 at 02:10:54PM +1000, Andreas Bauer wrote:
> + (define_insn "*sibcall_0"
> +   [(call (mem:QI (match_operand 0 "constant_call_address_operand" "s,c,d,a"))
> + 	 (match_operand 1 "" ""))]
> +   "SIBLING_CALL_P (insn)"
> + {
> +   if (SIBLING_CALL_P (insn))

Note that you're checking SIBLING_CALL_P here twice.  Note that
the call pattern from which you duplicated this now contains
references to SIBLING_CALL_P which should always be false.  All
of your patterns are doing this.

Note that constant_call_address_operand really means constant.
You cannot have register alternatives.

Don't be so tentative with respect to x86_64.  Yes, we _could_
do better than ecx/edx/eax, but those are a good start.

> + (define_insn "*sibcall_value_1"
> +   [(call (mem:QI (match_operand:SI 0 "call_insn_operand" "s,c,d,a"))
> + 	 (match_operand 1 "" ""))]

This is not a call value pattern.  There's no value.  Contrast
this with the sibcall_value_0 pattern which is correct.


r~

  parent reply	other threads:[~2002-09-23 22:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-22 21:11 Andreas Bauer
2002-09-23  3:03 ` Fergus Henderson
2002-09-23 12:25   ` Zack Weinberg
2002-09-23 16:52     ` Andreas Bauer
2002-09-23 17:10     ` Fergus Henderson
2002-09-23 21:27     ` Andreas Bauer
2002-09-23 21:37       ` Andrew Pinski
2002-09-23 21:44         ` Andreas Bauer
2002-09-23 21:48       ` Zack Weinberg
2002-09-23 22:14       ` Richard Henderson
2002-09-23 22:24       ` Richard Henderson
2002-09-24 22:24         ` Andreas Bauer
2002-09-24 23:28           ` Fergus Henderson
2002-09-25 16:47           ` Richard Henderson
2002-09-30  1:43             ` Andreas Bauer
2002-09-30  8:11               ` Fergus Henderson
2002-09-23 16:46   ` Andreas Bauer
2002-09-23 17:09     ` Richard Henderson
2002-09-23 15:12 ` Richard Henderson [this message]
2002-09-30  9:21 John David Anglin
2002-09-30 13:29 ` Hans-Peter Nilsson
2002-09-30 14:08   ` John David Anglin
2002-09-30 15:00     ` Hans-Peter Nilsson
2002-09-30 17:06     ` Richard Henderson
2002-09-30 17:44       ` John David Anglin
     [not found] <no.id>
2002-09-30 21:03 ` 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=20020923181211.K20637@redhat.com \
    --to=rth@redhat.com \
    --cc=baueran@in.tum.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason.ozolins@anu.edu.au \
    --cc=pizka@informatik.tu-muenchen.de \
    /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).