Message ID | 20150119175248.GA4362@arm.com |
---|---|
State | New |
Headers | show |
On Monday 2015-01-19 17:52, James Greenhalgh wrote:
> OK after the Cortex-A57 scheduling description goes in to the ARM port?
Yes, thanks, except that once will be sufficient. ;-) (The current
patch features the same hunk twice?)
Gerald
On Mon, Jan 19, 2015 at 08:57:31PM +0000, Gerald Pfeifer wrote: > On Monday 2015-01-19 17:52, James Greenhalgh wrote: > > OK after the Cortex-A57 scheduling description goes in to the ARM port? > > Yes, thanks, except that once will be sufficient. ;-) (The current > patch features the same hunk twice?) Once under AArch64 and once under ARM. I'm happy to drop one or the other hunk. Neither is incorrect, but I agree it is odd to say the same thing twice. Ramana, Marcus, Richard, any opinions on how you would like this resolved? Perhaps an ARM/AArch64 common changes section? Though I'm not sure which other changes would go in to it. Cheers, James
On 19/01/15 21:05, James Greenhalgh wrote: > On Mon, Jan 19, 2015 at 08:57:31PM +0000, Gerald Pfeifer wrote: >> On Monday 2015-01-19 17:52, James Greenhalgh wrote: >>> OK after the Cortex-A57 scheduling description goes in to the ARM port? >> >> Yes, thanks, except that once will be sufficient. ;-) (The current >> patch features the same hunk twice?) > > Once under AArch64 and once under ARM. I'm happy to drop one or the > other hunk. Neither is incorrect, but I agree it is odd to say the same > thing twice. > > Ramana, Marcus, Richard, any opinions on how you would like this resolved? > Perhaps an ARM/AArch64 common changes section? Though I'm not sure which > other changes would go in to it. > I'm not sure if a "common" section improves readability. I'd rather this remained as it is today. My 10 paise. Ramana > Cheers, > James >
On 19/01/15 21:05, James Greenhalgh wrote: > On Mon, Jan 19, 2015 at 08:57:31PM +0000, Gerald Pfeifer wrote: >> On Monday 2015-01-19 17:52, James Greenhalgh wrote: >>> OK after the Cortex-A57 scheduling description goes in to the ARM port? >> >> Yes, thanks, except that once will be sufficient. ;-) (The current >> patch features the same hunk twice?) > > Once under AArch64 and once under ARM. I'm happy to drop one or the > other hunk. Neither is incorrect, but I agree it is odd to say the same > thing twice. > > Ramana, Marcus, Richard, any opinions on how you would like this resolved? > Perhaps an ARM/AArch64 common changes section? Though I'm not sure which > other changes would go in to it. I'd prefer separate sections, IMHO that is more useful. /Marcus
On Tuesday 2015-01-20 08:15, Ramana Radhakrishnan wrote: > I'm not sure if a "common" section improves readability. I'd rather > this remained as it is today. On Tuesday 2015-01-20 09:27, Marcus Shawcroft wrote: > I'd prefer separate sections, IMHO that is more useful. /Marcus Okay, then let's go that way. Gerald
Index: htdocs/gcc-5/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/changes.html,v retrieving revision 1.65 diff -u -r1.65 changes.html --- htdocs/gcc-5/changes.html 14 Jan 2015 11:59:44 -0000 1.65 +++ htdocs/gcc-5/changes.html 16 Jan 2015 16:10:10 -0000 @@ -439,6 +439,12 @@ <h3 id="aarch64">AArch64</h3> <ul> + <li>Code generation for the ARM Cortex-A57 processor has been improved. + A more accurate instruction scheduling model for the processor is + now used, and a number of compiler tuning parameters have been set + to offer increased performance when compiling with + <code>-mcpu=cortex-a57</code> or <code>-mtune=cortex-a57</code>. + </li> <li> A workaround for the ARM Cortex-A53 erratum 835769 has been added and can be enabled by giving the <code>-mfix-cortex-a53-835769</code> option. @@ -471,6 +477,12 @@ configure option with either of <code>--with-tune</code> or <code>--with-arch</code>. </li> + <li>Code generation for the ARM Cortex-A57 processor has been improved. + A more accurate instruction scheduling model for the processor is + now used, and a number of compiler tuning parameters have been set + to offer increased performance when compiling with + <code>-mcpu=cortex-a57</code> or <code>-mtune=cortex-a57</code>. + </li> <li> Support for the Cortex-A17 processor has been added through the <code>-mcpu=cortex-a17</code> and <code>-mtune=cortex-a17</code> options. </li>