From: "bin.cheng" <bin.cheng@arm.com>
To: "Richard Earnshaw" <Richard.Earnshaw@arm.com>
Cc: "gcc-patches List" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH ARM] Improve ARM memset inlining
Date: Wed, 28 May 2014 08:53:00 -0000 [thread overview]
Message-ID: <000c01cf7a52$32202c70$96608550$@arm.com> (raw)
In-Reply-To: <CAHFci2_4hYWmB1FmMGTz7UgdQwFgseJRxo+K8RPoeyAqd+BiNQ@mail.gmail.com>
Ping^3
> -----Original Message-----
> From: Bin.Cheng [mailto:amker.cheng@gmail.com]
> Sent: Monday, May 19, 2014 2:40 PM
> To: Bin Cheng
> Cc: Richard Earnshaw; gcc-patches List
> Subject: Re: [PATCH ARM] Improve ARM memset inlining
>
> Ping^2
>
> Thanks,
> bin
>
> On Mon, May 12, 2014 at 11:17 AM, Bin.Cheng <amker.cheng@gmail.com>
> wrote:
> > Ping.
> >
> > Thanks,
> > bin
> >
> > On Tue, May 6, 2014 at 12:59 PM, bin.cheng <bin.cheng@arm.com> wrote:
> >>
> >>
>
> >> Precisely, I configured gcc with options "--with-arch=armv7-a
> >> --with-cpu|--with-tune=cortex-a9".
> >> I read gcc documents and realized that "-mcpu" is ignored when
> >> "-march" is specified. I don't know why gcc acts in this manner, but
> >> it leads to inconsistent configuration/command line behavior.
> >> If we configure GCC with "--with-arch=armv7-a --with-cpu=cortex-a9",
> >> then only "-march=armv7-a" is passed to cc1.
> >> If we compile with "-march=armv7-a -mcpu=cortex-a9", then gcc works
> >> fine and passes "-march=armv7-a -mcpu=cortex-a9" to cc1.
> >>
> >> Even more weird cc1 warns that "switch -mcpu=cortex-m4 conflicts with
> >> -march=armv7-m switch".
> >>
> >> Thanks,
> >> bin
> >>
> >>
> >>
> >>
> >
> >
> >
> > --
> > Best Regards.
>
>
>
> --
> Best Regards.
next prev parent reply other threads:[~2014-05-28 8:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 5:56 bin.cheng
2014-05-02 13:59 ` Richard Earnshaw
2014-05-05 7:21 ` bin.cheng
2014-05-06 5:00 ` bin.cheng
2014-05-12 3:17 ` Bin.Cheng
2014-05-19 6:40 ` Bin.Cheng
2014-05-28 8:53 ` bin.cheng [this message]
2014-06-04 9:11 ` bin.cheng
2014-06-27 8:21 ` Ramana Radhakrishnan
2014-07-04 12:18 ` Bin Cheng
2014-07-08 8:32 ` Bin.Cheng
2014-07-08 8:56 ` Ramana Radhakrishnan
2014-07-08 9:57 ` Bin.Cheng
2014-07-21 12:45 ` Bin.Cheng
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='000c01cf7a52$32202c70$96608550$@arm.com' \
--to=bin.cheng@arm.com \
--cc=Richard.Earnshaw@arm.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).