public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: Problem in split_basic_block
Date: Thu, 07 Aug 2003 22:45:00 -0000	[thread overview]
Message-ID: <20030807213839.GG12906@redhat.com> (raw)
In-Reply-To: <10308072038.AA09411@vlsi1.ultra.nyu.edu>

On Thu, Aug 07, 2003 at 04:38:04PM -0400, Richard Kenner wrote:
> I'm pretty sure not: it's only HPUX that's using it.  They are handling
> it the same way as VMS on Alpha.

Well, the thing is, they needn't set up the segments in any way
that's actually screwy.  They *can* lay them out nicely sequential.

But if you don't use addp4, you wind up with extra sext insns all
the time.  Unlike Alpha, there's no add instruction that sign (or
zero) extends from 32-bits.

None of my business, I guess.


r~

  reply	other threads:[~2003-08-07 21:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07 21:08 Richard Kenner
2003-08-07 22:45 ` Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-10 16:35 Richard Kenner
2003-08-08 23:53 Richard Kenner
2003-08-08  3:04 Richard Kenner
2003-08-10  8:06 ` Jim Wilson
2003-08-07 20:30 Richard Kenner
2003-08-07 19:30 Nathanael Nerode
2003-08-07 13:10 Richard Kenner
2003-08-07  7:01 Richard Kenner
2003-08-07 19:33 ` Geoff Keating
2003-08-07  5:32 Richard Kenner
2003-08-06 23:42 Richard Kenner
2003-08-06 23:47 ` Zack Weinberg
2003-08-06 23:56   ` Douglas B Rupp
2003-08-06 23:57     ` Zack Weinberg
2003-08-07  0:16       ` Douglas B Rupp
2003-08-07  0:40         ` Zack Weinberg
2003-08-06 23:57   ` Douglas B Rupp
2003-08-07  0:43     ` Zack Weinberg
2003-08-07  0:38   ` Douglas B Rupp
2003-08-07  1:05     ` Zack Weinberg
2003-08-07 20:59 ` Richard Henderson
2003-08-08 23:41 ` Richard Henderson
2003-09-01 13:18   ` Olivier Hainque
2003-08-01 23:07 Richard Kenner
2003-08-06 22:41 ` Richard Henderson

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=20030807213839.GG12906@redhat.com \
    --to=rth@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    /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).