From: Denis Chertykov <chertykov@gmail.com>
To: "S, Pitchumani" <Pitchumani.S@atmel.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [patch,avr] device specific instruction support for avr devices
Date: Tue, 25 Mar 2014 17:07:00 -0000 [thread overview]
Message-ID: <CADOs=zZFb7rzC4teAXckz4s0Wz4SqW3Qn+Q8zxNn0tfJcn9fsg@mail.gmail.com> (raw)
In-Reply-To: <CAC140656783604CABA6AE60C2A6D5A46AE13B14@penmbx01>
2014-03-24 12:23 GMT+04:00 S, Pitchumani <Pitchumani.S@atmel.com>:
>> -----Original Message-----
>> From: binutils-owner@sourceware.org [mailto:binutils-owner@sourceware.org]
>> On Behalf Of S, Pitchumani
>> Sent: Monday, March 03, 2014 11:21 AM
>> To: binutils@sourceware.org
>> Cc: chertykov@gmail.com
>> Subject: [patch,avr] device specific instruction support for avr devices
>>
>> Hi,
>>
>> Few AVR Xmega devices have specific instruction support than the
>> architecture
>> it belongs to. For example atxmega128b1 device has RMW instructions
>> (XCH,LAC,
>> LAS and LAT) support, but not all avrxmega6 devices have.
>>
>> Now, avr-gcc passes architecture name to assembler instead of device name.
>> So,
>> RMW instructions are not recognized (illegal opcode error) by assembler.
>>
>> I have attached a patch to address this issue in assembler.
>> - It adds a option '-mrmw' to assembler.
>> - Based on -mrmw option device specific instructions are added to current
>> instruction set (mcu_types[i].isa | AVR_ISA_RMW)
>> Now assembler can recognize rmw instructions for respective devices.
>>
>> It is necessary to update gcc to pass -mrmw option to assembler if the
>> selected device has rmw instructions. I'll send a patch for gcc as well.
>>
>> Please review the attached patch and give your suggestions.
>
> Hi,
>
> I have updated the patch to include -mrmw option to binutils.
Where is the patch ?
Denis.
next prev parent reply other threads:[~2014-03-25 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 5:50 S, Pitchumani
2014-03-24 8:23 ` S, Pitchumani
2014-03-25 17:07 ` Denis Chertykov [this message]
2014-03-27 5:07 ` S, Pitchumani
2014-03-29 5:55 ` Denis Chertykov
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='CADOs=zZFb7rzC4teAXckz4s0Wz4SqW3Qn+Q8zxNn0tfJcn9fsg@mail.gmail.com' \
--to=chertykov@gmail.com \
--cc=Pitchumani.S@atmel.com \
--cc=binutils@sourceware.org \
/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).