From: Nick Clifton <nickc@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Bridge Wu <mingqiao.wu@gmail.com>, binutils <binutils@sourceware.org>
Subject: Re: iwmmxt2 patch for binutils-2.16.92
Date: Mon, 25 Sep 2006 16:20:00 -0000 [thread overview]
Message-ID: <45180006.2010006@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0609191917450.27932@digraph.polyomino.org.uk>
Hi Joseph,
> bfd/
> 2006-09-19 Mark Shinwell <shinwell@codesourcery.com>
> Joseph Myers <joseph@codesourcery.com>
> Ian Lance Taylor <ian@wasabisystems.com>
> Ben Elliston <bje@wasabisystems.com>
>
> * archures.c: Add definition for bfd_mach_arm_iWMMXt2.
> * cpu-arm.c (processors): Add bfd_mach_arm_iWMMXt2.
> (arch_info_struct, bfd_arm_update_notes): Likewise.
> (architectures): Likewise.
> (bfd_arm_merge_machines): Check for iWMMXt2.
> * bfd-in2.h: Rebuild.
>
> gas/
> 2006-09-19 Mark Shinwell <shinwell@codesourcery.com>
> Joseph Myers <joseph@codesourcery.com>
> Ian Lance Taylor <ian@wasabisystems.com>
> Ben Elliston <bje@wasabisystems.com>
>
> * config/tc-arm.c (arm_cext_iwmmxt2): New.
> (enum operand_parse_code): New code OP_RIWR_I32z.
> (parse_operands): Handle OP_RIWR_I32z.
> (do_iwmmxt_wmerge): New function.
> (do_iwmmxt_wldstd): Handle iwmmxt2 case where second operand is
> a register.
> (do_iwmmxt_wrwrwr_or_imm5): New function.
> (insns): Mark instructions as RIWR_I32z as appropriate.
> Also add torvsc<b,h,w>, wabs<b,h,w>, wabsdiff<b,h,w>,
> waddbhus<l,m>, waddhc, waddwc, waddsubhx, wavg4{r}, wmaddu{x,n},
> wmadds{x,n}, wmerge, wmiaxy{n}, wmiawxy{n}, wmul<sm,um>{r},
> wmulw<um,sm,l>{r}, wqmiaxy{n}, wqmulm{r}, wqmulwm{r}, wsubaddhx.
> (md_begin): Handle IWMMXT2.
> (arm_cpus): Add iwmmxt2.
> (arm_extensions): Likewise.
> (arm_archs): Likewise.
>
> gas/testsuite/
> 2006-09-19 Mark Shinwell <shinwell@codesourcery.com>
> Joseph Myers <joseph@codesourcery.com>
> Ian Lance Taylor <ian@wasabisystems.com>
> Ben Elliston <bje@wasabisystems.com>
>
> * gas/arm/iwmmxt2.s: New file.
> * gas/arm/iwmmxt2.d: New file.
>
> include/opcode/
> 2006-09-19 Mark Shinwell <shinwell@codesourcery.com>
> Joseph Myers <joseph@codesourcery.com>
> Ian Lance Taylor <ian@wasabisystems.com>
> Ben Elliston <bje@wasabisystems.com>
>
> * arm.h (ARM_CEXT_IWMMXT2, ARM_ARCH_IWMMXT2): Define.
>
> opcodes/
> 2006-09-19 Mark Shinwell <shinwell@codesourcery.com>
> Joseph Myers <joseph@codesourcery.com>
> Ian Lance Taylor <ian@wasabisystems.com>
> Ben Elliston <bje@wasabisystems.com>
>
> * arm-dis.c (coprocessor_opcodes): The X-qualifier to WMADD may
> only be used with the default multiply-add operation, so if N is
> set, don't bother printing X. Add new iwmmxt instructions.
> (IWMMXT_INSN_COUNT): Update.
> (iwmmxt_wwssnames): Qualify "wwss" names at index 2, 6, 10 and 14
> with a 'c' suffix.
> (print_insn_coprocessor): Check for iWMMXt2. Handle format
> specifiers 'r', 'i'.
Approved - please apply.
Cheers
Nick
next prev parent reply other threads:[~2006-09-25 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 13:41 Bridge Wu
2006-09-19 14:21 ` Joseph S. Myers
2006-09-19 20:58 ` Joseph S. Myers
2006-09-20 5:20 ` Bridge Wu
2006-09-20 14:39 ` Joseph S. Myers
2006-09-21 5:31 ` Bridge Wu
2006-09-21 14:06 ` Joseph S. Myers
2006-09-25 16:20 ` Nick Clifton [this message]
2006-09-26 10:41 ` Bridge Wu
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=45180006.2010006@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=mingqiao.wu@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).