public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Olivier Hainque <hainque@ACT-Europe.FR>
Cc: Jan Hubicka <jh@suse.cz>, Michael Matz <matz@suse.de>, gcc@gcc.gnu.org
Subject: Re: Question on fixup_abnormal_edges
Date: Tue, 15 Oct 2002 17:03:00 -0000	[thread overview]
Message-ID: <20021015230235.GM25225@redhat.com> (raw)
In-Reply-To: <20021015124700.A11376@berlin.int.act-europe.fr>

On Tue, Oct 15, 2002 at 12:47:00PM +0200, Olivier Hainque wrote:
> What I'm first unclear about is:
> 
> When using table driven EH, is it expected that possibly call clobbered hard
> registers get assigned to pseudos live across calls like in the case above ?

Well, except for caller-save not being intelligent enough to
add the instruction to the edge, rather than directly after
the call instruction, everything would have worked out ok.

Off-hand I don't know caller-save well enough to know how easy
it would be to (1) fix this or (2) disable allocation of call
clobbered hard regs to pseudos live across ABCALL/EH edges.


r~

  reply	other threads:[~2002-10-15 23:02 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01  2:06 Olivier Hainque
2002-10-01  2:08 ` Jan Hubicka
2002-10-01  2:57   ` Olivier Hainque
2002-10-01  3:00   ` Michael Matz
2002-10-01  3:03     ` Michael Matz
2002-10-01  3:40       ` Olivier Hainque
2002-10-01  4:23         ` Jan Hubicka
2002-10-01  6:49           ` Olivier Hainque
2002-10-01  7:02             ` Jan Hubicka
2002-10-01  7:08               ` Olivier Hainque
2002-10-01  7:12                 ` Jan Hubicka
2002-10-01  8:44                   ` Olivier Hainque
2002-10-01  9:08                     ` Jan Hubicka
2002-10-01  9:46                       ` Olivier Hainque
2002-10-01 12:24                         ` Michael Matz
2002-10-02 14:11                           ` Olivier Hainque
2002-10-03  6:20                             ` Jan Hubicka
2002-10-03  6:26                               ` Olivier Hainque
2002-10-03  6:51                                 ` Jan Hubicka
2002-10-03  8:06                                   ` Olivier Hainque
2002-10-03  8:19                                     ` Jan Hubicka
2002-10-15  5:35                                       ` Olivier Hainque
2002-10-15 17:03                                         ` Richard Henderson [this message]
2002-10-16  2:58                                           ` Olivier Hainque
2002-10-16  4:02                                           ` Michael Matz
2002-10-16  4:06                                             ` Jan Hubicka
2002-10-16  4:45                                               ` Michael Matz
2002-10-16  5:01                                                 ` Jan Hubicka
2002-10-16 10:29                                                   ` Richard Henderson
2002-10-16 10:26                                             ` Richard Henderson
2002-10-01  4:43         ` Michael Matz
2002-10-01  4:46           ` Jan Hubicka
2002-10-15  6:10 Richard Kenner
2002-10-15  7:47 ` Michael Matz
2002-10-15  9:25   ` Michael Matz
2002-10-16  0:31 Richard Kenner
2002-10-16  2:31 ` Richard Henderson
2002-10-16  7:08 Richard Kenner
2002-10-21 11:50 ` Jeff Law
2002-10-21 11:54   ` David S. Miller
2002-10-16  7:12 Richard Kenner

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=20021015230235.GM25225@redhat.com \
    --to=rth@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hainque@ACT-Europe.FR \
    --cc=jh@suse.cz \
    --cc=matz@suse.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).