From: Andreas Krebbel <Andreas.Krebbel@de.ibm.com>
To: Rask Ingemann Lambertsen <rask@sygehus.dk>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] lower-subreg: Decompose multiword shifts
Date: Thu, 02 Aug 2007 19:21:00 -0000 [thread overview]
Message-ID: <20070802192140.GA32685@de.ibm.com> (raw)
In-Reply-To: <20070802185148.GJ25795@sygehus.dk>
Hello,
> Why isn't the same magic happening on s390?
Your target does not seem to provide shift instructions dealing with
register pairs. So I would guess that optab already decomposes such
shifts for you - right?! At least I don't see an SI mode shift in the
RTL pieces you've sent. Certainly that optimization only makes sense if
your back end provides such an instruction.
> > + typedef unsigned int u32;
> > + typedef unsigned long long u64;
>
> Please use uint32_t and uint64_t from stdint.h (or some other reliable
> means of getting types of the sizes you want).
Yes the names I've choosen aren't correct for any platform but I think the types are nevertheless a good choice considering that I need something as wide as register and something else with twice the size.
Looks like an ideal place for using __attribute__((mode(word))) ;)
Bye,
-Andreas-
next prev parent reply other threads:[~2007-08-02 19:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 15:35 Andreas Krebbel
2007-08-02 16:56 ` Paolo Bonzini
2007-08-03 16:41 ` Andreas Krebbel
2007-08-03 19:02 ` Paolo Bonzini
2007-08-02 18:52 ` Rask Ingemann Lambertsen
2007-08-02 19:21 ` Andreas Krebbel [this message]
2007-08-07 1:41 ` Rask Ingemann Lambertsen
2007-08-07 8:29 ` Andreas Krebbel
2007-08-02 23:16 ` Rask Ingemann Lambertsen
2007-08-03 12:03 ` Michael Matz
2007-08-03 14:34 ` Andreas Krebbel
2007-08-03 15:37 ` Michael Matz
2007-08-07 1:08 ` Ian Lance Taylor
2007-08-07 1:27 ` Ian Lance Taylor
2007-08-07 10:47 ` Andreas Krebbel
2007-08-08 18:40 ` Andreas Tobler
2007-08-09 7:45 ` Andreas Krebbel
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=20070802192140.GA32685@de.ibm.com \
--to=andreas.krebbel@de.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rask@sygehus.dk \
/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).