From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: Christian Bruel <christian.bruel@st.com>
Cc: Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
richard Earnshaw <Richard.Earnshaw@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: ping: [PATCH, ARM] attribute target (thumb,arm) [0-6]
Date: Tue, 14 Apr 2015 19:11:00 -0000 [thread overview]
Message-ID: <CAJA7tRZGiPVXpWj8i-eDpvsXXtVscCuaS_v-2XM4Zqv-R2Rccg@mail.gmail.com> (raw)
In-Reply-To: <54D8A94E.3010603@st.com>
On Mon, Feb 9, 2015 at 12:34 PM, Christian Bruel <christian.bruel@st.com> wrote:
> Hello,
>
> I'd like to ping with a respin of the 7 patches for
> the attribute target (thumb,arm) [0-6] :
>
> https://gcc.gnu.org/ml/gcc-patches/2014-11/msg02455.html
> https://gcc.gnu.org/ml/gcc-patches/2014-11/msg02458.html
> https://gcc.gnu.org/ml/gcc-patches/2014-11/msg02460.html
> https://gcc.gnu.org/ml/gcc-patches/2014-11/msg02461.html
> https://gcc.gnu.org/ml/gcc-patches/2014-11/msg02463.html
> https://gcc.gnu.org/ml/gcc-patches/2014-11/msg02467.html
> https://gcc.gnu.org/ml/gcc-patches/2014-11/msg02468.html
>
> In order to fix the various conflicts that have happened since, please find
> attached the re-based patches to trunk rev #220529 (respectively from above
> p0.patch, p1.patch, p2,patch, p3.patch, p4,patch, p5,patch, p6,patch).
>
> I understand the difficulty of reviewing those due to the code
> reorganization, but maintaining them are really a pain since a conflict
> happens at almost every update in the ARM back-end :-(
>
> Comments, questions are welcome,
>
> Many thanks
>
> Christian
>
>
>
>
Can you respin this now that we are in stage1 again ?
Ramana
next prev parent reply other threads:[~2015-04-14 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 12:34 Christian Bruel
2015-02-09 12:45 ` Christian Bruel
2015-04-14 19:11 ` Ramana Radhakrishnan [this message]
2015-04-20 8:35 ` Christian Bruel
2015-04-30 8:27 ` Ramana Radhakrishnan
2015-04-30 8:41 ` Christian Bruel
2015-04-30 10:26 ` Ramana Radhakrishnan
2015-05-20 13:13 ` Christian Bruel
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=CAJA7tRZGiPVXpWj8i-eDpvsXXtVscCuaS_v-2XM4Zqv-R2Rccg@mail.gmail.com \
--to=ramana.gcc@googlemail.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=christian.bruel@st.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ramrad01@arm.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).