On July 24, 2018 5:50:33 PM GMT+02:00, Ramana Radhakrishnan
wrote:
>On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener
>wrote:
>>
>> Status
>> ==
>>
>> The GCC 8 branch is frozen for preparation of the GCC 8.2 release.
>> All changes to the branch now require release manager approval.
>>
>>
>>
On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener wrote:
>
> Status
> ==
>
> The GCC 8 branch is frozen for preparation of the GCC 8.2 release.
> All changes to the branch now require release manager approval.
>
>
> Previous Report
> ===
>
> https://gcc.gnu.org/ml/gcc/2018-07/msg001
Hello
We have a client who is interested in some of your services. I
will provide further details should we get a response from you.
Kind regards
Mr J. Hamilton
CEO
Hamtons Merchants Trading Co. Int'l
On 24/07/18 09:40, Fredrik Hederstierna wrote:
> Hi
>
> This is a general question to all you working with GCC benchmarking.
>
> I have been working with code benchmarks like CSiBE for ARM. From
> time to time unpredicted results appears where numbers gets worse by
> no reason.
>
> When looking
On Tue, 24 Jul 2018, Fredrik Hederstierna wrote:
> So my question is how to approach this problems when doing benchmarking,
> ofcourse we want the benchmark to mirror as near as 'real life' code as
> possible. But if code contains real bugs, and issues that could cause
> unpredictable code genera
Hi
This is a general question to all you working with GCC benchmarking.
I have been working with code benchmarks like CSiBE for ARM.
>From time to time unpredicted results appears where numbers gets worse by no
>reason.
When looking into what could cause this unpredictable behaviour, I found th
