From: Richard Henderson <rth@redhat.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Steve Ellcey <sje@cup.hp.com>
Subject: Re: [Patch IA64]: Fix 32 bits tablejump
Date: Fri, 16 Mar 2012 15:15:00 -0000 [thread overview]
Message-ID: <4F6358C2.1090907@redhat.com> (raw)
In-Reply-To: <970B4B24-81CF-45EA-94FF-7649505059F0@adacore.com>
On 03/16/12 04:56, Tristan Gingold wrote:
> 2012-03-16 Tristan Gingold <gingold@adacore.com>
>
> * config/ia64/vms.h (CASE_VECTOR_MODE): Define.
> * config/ia64/ia64.md: Remove mode in template.
> Sign extend operand in expand_simple_binop.
> * config/ia64/ia64.h (ASM_OUTPUT_ADDR_DIFF_ELT): Use
> CASE_VECTOR_MODE instead of TARGET_ILP32.
> (ADDR_VEC_ALIGN): Make it depends on CASE_VECTOR_MODE.
Ok.
r~
next prev parent reply other threads:[~2012-03-16 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 11:56 Tristan Gingold
2012-03-16 15:15 ` Richard Henderson [this message]
2012-03-27 9:48 ` Tristan Gingold
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=4F6358C2.1090907@redhat.com \
--to=rth@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gingold@adacore.com \
--cc=sje@cup.hp.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).