From: Andrew Burgess <andrew.burgess@embecosm.com>
To: binutils@sourceware.org
Cc: Claudiu.Zissulescu@synopsys.com, Cupertino.Miranda@synopsys.com,
Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [PATCH 0/4] [ARC] Set of miscellaneous fixes
Date: Wed, 11 May 2016 19:21:00 -0000 [thread overview]
Message-ID: <1462994486-12419-1-git-send-email-andrew.burgess@embecosm.com> (raw)
A set of fixes, they are all disjoint I've grouped them simply because
they are all ARC related.
--
Andrew Burgess (4):
gas/arc: Add guard against operand array overflow.
gas/arc: Fix array overrun when checking opcode array
gas/arc: Use BFD_VMA_FMT for printf format specifier
gas/arc: Make member of arc_flags const
gas/ChangeLog | 27 +++++++++++++++++++++++++++
gas/config/tc-arc.c | 28 ++++++++++++++++------------
gas/config/tc-arc.h | 2 +-
gas/testsuite/gas/arc/asm-errors-2.d | 2 ++
gas/testsuite/gas/arc/asm-errors-2.err | 2 ++
gas/testsuite/gas/arc/asm-errors-2.s | 2 ++
gas/testsuite/gas/arc/asm-errors.err | 2 ++
gas/testsuite/gas/arc/asm-errors.s | 1 +
8 files changed, 53 insertions(+), 13 deletions(-)
create mode 100644 gas/testsuite/gas/arc/asm-errors-2.d
create mode 100644 gas/testsuite/gas/arc/asm-errors-2.err
create mode 100644 gas/testsuite/gas/arc/asm-errors-2.s
--
2.6.4
next reply other threads:[~2016-05-11 19:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 19:21 Andrew Burgess [this message]
2016-05-11 19:21 ` [PATCH 2/4] gas/arc: Fix array overrun when checking opcode array Andrew Burgess
2016-05-12 12:24 ` Claudiu Zissulescu
2016-05-18 11:30 ` Nick Clifton
2016-05-11 19:21 ` [PATCH 3/4] gas/arc: Use BFD_VMA_FMT for printf format specifier Andrew Burgess
2016-05-12 12:27 ` Claudiu Zissulescu
2016-05-18 11:28 ` Nick Clifton
2016-05-11 19:21 ` [PATCH 4/4] gas/arc: Make member of arc_flags const Andrew Burgess
2016-05-12 12:28 ` Claudiu Zissulescu
2016-05-18 11:28 ` Nick Clifton
2016-05-11 19:21 ` [PATCH 1/4] gas/arc: Add guard against operand array overflow Andrew Burgess
2016-05-12 12:23 ` Claudiu Zissulescu
2016-05-18 11:31 ` Nick Clifton
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=1462994486-12419-1-git-send-email-andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=Claudiu.Zissulescu@synopsys.com \
--cc=Cupertino.Miranda@synopsys.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).