From: Claudiu Zissulescu <claudiu.zissulescu@synopsys.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "francois.bedard@synopsys.com" <francois.bedard@synopsys.com>,
"andrew.burgess@embecosm.com" <andrew.burgess@embecosm.com>
Subject: RE: [PATCH 0/2][ARC] Fixes needed for the upcomming release.
Date: Fri, 14 Dec 2018 10:45:00 -0000 [thread overview]
Message-ID: <098ECE41A0A6114BB2A07F1EC238DE8966816EEC@de02wembxa.internal.synopsys.com> (raw)
In-Reply-To: <20181211102335.4643-1-claziss@gmail.com>
Thank you Andrew for your quick review. Both patches are committed.
Claudiu
________________________________________
From: Claudiu Zissulescu [claziss@gmail.com]
Sent: Tuesday, December 11, 2018 11:23 AM
To: gcc-patches@gcc.gnu.org
Cc: francois.bedard@synopsys.com; claudiu.zissulescu@synopsys.com; andrew.burgess@embecosm.com
Subject: [PATCH 0/2][ARC] Fixes needed for the upcomming release.
Hi Andrew,
Please find two small patches which are fixing a number of issues found in the upcomming release.
Ok to apply?
Claudiu
Claudiu Zissulescu (2):
[ARC] Fix REG_CLASS_NAMES
[ARC] Fix millicode wrong blink restore.
gcc/config/arc/arc.c | 4 +---
gcc/config/arc/arc.h | 1 +
gcc/testsuite/gcc.target/arc/milli-1.c | 23 +++++++++++++++++++++++
3 files changed, 25 insertions(+), 3 deletions(-)
create mode 100644 gcc/testsuite/gcc.target/arc/milli-1.c
--
2.19.1
prev parent reply other threads:[~2018-12-14 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 10:23 Claudiu Zissulescu
2018-12-11 10:23 ` [PATCH 2/2] [ARC] Fix millicode wrong blink restore Claudiu Zissulescu
2018-12-12 16:18 ` Andrew Burgess
2018-12-11 10:23 ` [PATCH 1/2] [ARC] Fix REG_CLASS_NAMES Claudiu Zissulescu
2018-12-12 16:16 ` Andrew Burgess
2018-12-14 10:45 ` Claudiu Zissulescu [this message]
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=098ECE41A0A6114BB2A07F1EC238DE8966816EEC@de02wembxa.internal.synopsys.com \
--to=claudiu.zissulescu@synopsys.com \
--cc=andrew.burgess@embecosm.com \
--cc=francois.bedard@synopsys.com \
--cc=gcc-patches@gcc.gnu.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).