On 10/07/2015 08:07 PM, pins...@gmail.com wrote:
Yes. But I am saying some one could do -fprofile-use -frename-registers and
expect rename registers to stay on even if there is no profile.
That's true, we shouldn't disable any options that were explicitly
requested by
the user.
Why not
On Thu, Oct 8, 2015 at 9:54 AM, Nikolai Bozhenov wrote:
>
> On 10/07/2015 08:07 PM, pins...@gmail.com wrote:
>>
>> Yes. But I am saying some one could do -fprofile-use -frename-registers
>> and expect rename registers to stay on even if there is no profile.
>
>
> That's
On Wed, Oct 7, 2015 at 9:11 AM, Maxim Ostapenko
wrote:
> Hi,
>
> when testing OpenSSL performance, I found out that sometimes PGO-built
> binaries can actually introduce performance regressions. We could identify
> affected object files and disable PGO for them by
Hi,
when testing OpenSSL performance, I found out that sometimes PGO-built
binaries can actually introduce performance regressions. We could
identify affected object files and disable PGO for them by simply
removing corresponding .gcda file. However, even if profile data is not
presented,
On 07/10/15 19:18, Andrew Pinski wrote:
On Wed, Oct 7, 2015 at 9:11 AM, Maxim Ostapenko
wrote:
Hi,
when testing OpenSSL performance, I found out that sometimes PGO-built
binaries can actually introduce performance regressions. We could identify
affected
On 2015.10.07 at 19:11 +0300, Maxim Ostapenko wrote:
> when testing OpenSSL performance, I found out that sometimes PGO-built
> binaries can actually introduce performance regressions. We could
> identify affected object files and disable PGO for them by simply
> removing corresponding .gcda
> On Oct 7, 2015, at 9:28 AM, Maxim Ostapenko
> wrote:
>
>
>
>> On 07/10/15 19:18, Andrew Pinski wrote:
>> On Wed, Oct 7, 2015 at 9:11 AM, Maxim Ostapenko
>> wrote:
>>> Hi,
>>>
>>> when testing OpenSSL performance, I found