Hi James, > This patch is OK for trunk. Thank you for the review and merging the patch to trunk.
> I couldn't spot your name in the MAINTAINERS file, so I've applied this > on your behalf as revision 237645. My name is not present in the MAINTAINERS file. This was my first patch in the GCC :-) In future I will request aarch64's maintainers to apply the patches on my behalf after review (to avoid any confusion). Thanks. with regards, Virendra Pathak On Tue, Jun 21, 2016 at 7:16 PM, James Greenhalgh <james.greenha...@arm.com> wrote: > > On Sat, Jun 18, 2016 at 01:57:43AM +0530, Virendra Pathak wrote: > > Hi, > > > > Please find the patch for introducing vulcan as a cpu name for the > > AArch64 port of GCC. > > Broadcom's vulcan is an armv8.1-a aarch64 server processor. > > > > Since vulcan is the first armv8.1-a processor to be introduced in > > aarch64-cores.def, > > I have created a new section in the file for the armv8.1 based processors. > > Kindly let me know if that is okay. > > > > Tested the patch with cross aarch64-linux-gnu, bootstrapped native > > aarch64-unknown-linux-gnu > > and make check (gcc, ld, gas, binutils, gdb). > > No new regression failure is added by this patch. > > > > In addition, tested -mcpu=vulcan -mtune=vulcan flags by passing them > > via command line. > > Also verified that above flags passes armv8.1-a option to assembler(as). > > > > At present we are using schedule & cost model of cortex-a57 but > > soon we will be submitting one for vulcan. > > > > Please review the patch. > > Ok for trunk? > > > > This patch is OK for trunk. > > I couldn't spot your name in the MAINTAINERS file, so I've applied this > on your behalf as revision 237645. > > Thank you for the patch. > > Thanks, > James > > > gcc/ChangeLog: > > > > Virendra Pathak <virendra.pat...@broadcom.com> > > > > * config/aarch64/aarch64-cores.def (vulcan): New core. > > * config/aarch64/aarch64-tune.md: Regenerate. > > * doc/invoke.texi: Document vulcan as an available option. > > >
