From: Paul Brook <paul@codesourcery.com>
To: gcc@gcc.gnu.org
Cc: "Jan Hoogerbrugge" <jan.hoogerbrugge@gmail.com>
Subject: Re: subreg question
Date: Tue, 25 Mar 2008 15:58:00 -0000 [thread overview]
Message-ID: <200803251427.54214.paul@codesourcery.com> (raw)
In-Reply-To: <5afce4f40803250719n6ffd09c6h9ad4481ff7afdaf5@mail.gmail.com>
> How to tell gcc to insert high, low, and combine operations, when 32
> and 64 bit operations are exchanging values?
CANNOT_CHANGE_MODE_CLASS
Paul
next prev parent reply other threads:[~2008-03-25 14:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 14:56 Jan Hoogerbrugge
2008-03-25 15:58 ` Paul Brook [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-12 18:13 Dale Johannesen
2001-12-13 1:39 ` Jan Hubicka
2001-12-13 10:33 ` Aldy Hernandez
2001-12-13 12:26 ` Dale Johannesen
2001-12-13 12:39 ` Daniel Jacobowitz
2001-12-13 12:45 ` Dale Johannesen
2001-12-13 12:51 ` Daniel Jacobowitz
2001-12-13 13:04 ` Dale Johannesen
2001-12-13 13:33 ` Daniel Jacobowitz
2001-12-13 13:34 ` Aldy Hernandez
2001-12-13 14:56 ` Richard Henderson
2001-12-13 13:04 ` Aldy Hernandez
2001-12-13 14:57 ` Joe Buck
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=200803251427.54214.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=jan.hoogerbrugge@gmail.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).