Ping^4. The original thread is https://gcc.gnu.org/ml/gcc-patches/2014-05/msg00182.html, also there is some info at https://gcc.gnu.org/ml/gcc-patches/2014-05/msg00182.html in the same thread.
Thanks, bin > -----Original Message----- > From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches- > ow...@gcc.gnu.org] On Behalf Of bin.cheng > Sent: Wednesday, May 28, 2014 4:53 PM > To: Richard Earnshaw > Cc: gcc-patches List > Subject: RE: [PATCH ARM] Improve ARM memset inlining > > Ping^3 > > > -----Original Message----- > > From: Bin.Cheng [mailto:amker.ch...@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.ch...@gmail.com> > > wrote: > > > Ping. > > > > > > Thanks, > > > bin > > > > > > On Tue, May 6, 2014 at 12:59 PM, bin.cheng <bin.ch...@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. > > > >
