On Tue, 24 Jul 2012, Uros Bizjak wrote:
>> Also can I modify doc/invoke.texi now?
> OK for mainline SVN.
And, yes, I think you can update invoke.texi.
And add a note to the release notes at http://gcc.gnu.org/4.8/changes.html
;-)
Gerald
Hello!
> 2012-7-18 Venkataramanan Kumar
>
> Jaguar Enablement
> * config.gcc (i[34567]86-*-linux* | ...): Add btver2.
> (case ${target}): Add btver2.
> * config/i386/driver-i386.c (host_detect_local_cpu): Let
> -march=native recognize btver2 processors.
> * c
inek [mailto:ja...@redhat.com]
> Sent: Friday, July 20, 2012 10:31 PM
> To: Kumar, Venkataramanan
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH, i386]: AMD btver2 enablement
>
> On Fri, Jul 20, 2012 at 11:39:32AM -0500, venkataramanan.ku...@amd.com wrote:
> > Below p
On Fri, Jul 20, 2012 at 11:39:32AM -0500, venkataramanan.ku...@amd.com wrote:
> Below patch does the basic enablement for next generation AMD low power
> btver2 core.
> It defines -march=btver2 and -mtune=btver2, and lets -march=native correctly
> recognizes btver2. At the moment the tuning is mos
Hi Maintainers,
Below patch does the basic enablement for next generation AMD low power btver2
core.
It defines -march=btver2 and -mtune=btver2, and lets -march=native correctly
recognizes btver2. At the moment the tuning is mostly a copy of btver1.
The patch passed bootstrap and the x86 tests.
