public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <Ulrich.Weigand@de.ibm.com>
To: Richard Henderson <rth@redhat.com>
Cc: Jan Hubicka <jh@suse.cz>, gcc@gcc.gnu.org, aj@suse.de
Subject: Re: Profiling on S390
Date: Wed, 23 Apr 2003 12:19:00 -0000	[thread overview]
Message-ID: <OFE003A606.B6085565-ONC1256D11.003B52B2@de.ibm.com> (raw)


Richard Henderson wrote:

>It could, but if you don't have add/load/store insns that don't
>clobber CC, then you'll get in trouble with reload too.

We can load/store without clobbering CC; while we don't have
a general addition operation that does not clobber CC, we do
have a load-address operation, which is all reload actually
needs (if things are set up correctly).  However, LA is a 31-bit
addition and cannot be used to implement 32-bit or even 64-bit
integer arithmetic.

However, it is certainly true that the use of gen_add2_insn in
reload is really broken as it doesn't care at all whether CC
gets clobbered.  It is only by setting things up so that reload
actually never tries to use gen_add2_insn that things work out ...

>This is all about a movstrsi or cmpstrsi pattern?  Perhaps it
>would be better to keep this as one unit until after reload?

It's only about cmpstrsi.  The idea behind exposing the loop
early was to potentially benefit from loop unrolling ...


Mit freundlichen Gruessen / Best Regards

Ulrich Weigand

--
  Dr. Ulrich Weigand
  Linux for S/390 Design & Development
  IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032 Boeblingen
  Phone: +49-7031/16-3727   ---   Email: Ulrich.Weigand@de.ibm.com

             reply	other threads:[~2003-04-23 10:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 12:19 Ulrich Weigand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-23 21:50 Ulrich Weigand
2003-04-23 22:08 ` Richard Henderson
2003-04-23 18:18 Ulrich Weigand
2003-04-22 22:34 Ulrich Weigand
2003-04-22 23:13 ` Richard Henderson
2003-04-23 10:59   ` Jan Hubicka
2003-04-23 18:26     ` Richard Henderson
2003-04-23 19:18       ` Jan Hubicka
2003-04-23 19:56         ` Richard Henderson
2003-04-23 21:29           ` Jan Hubicka
2003-04-23 22:33             ` Richard Henderson
2003-04-25 17:01               ` Jan Hubicka
2003-04-18 12:11 Jan Hubicka

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=OFE003A606.B6085565-ONC1256D11.003B52B2@de.ibm.com \
    --to=ulrich.weigand@de.ibm.com \
    --cc=aj@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=jh@suse.cz \
    --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).