shoori - C51841
> Cc: gcc@gcc.gnu.org
> Subject: Re: 22% degradation seen in embench:matmult-int
>
> [You don't often get email from richard.guent...@gmail.com. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
>
> EXTERNAL EMAIL: Do not click links or
L: Do not click links or open attachments unless you know the
content is safe
On Wed, Feb 12, 2025 at 4:38 PM Visda.Vokhshoori--- via Gcc
wrote:
>
> Embench is used for benchmarking on embedded devices.
> This one project matmult-int has a function Multiply. It’s a matrix
> multiplic
* When we do the loop interchange on the one loop nest that get interchanged in
the program source it is slightly (.7%) faster.
From: Gcc on behalf of
Visda.Vokhshoori--- via Gcc
Date: Wednesday, February 12, 2025 at 10:38 AM
To: gcc@gcc.gnu.org
Subject: 22% degradation seen in
Embench is used for benchmarking on embedded devices.
This one project matmult-int has a function Multiply. It’s a matrix
multiplication for 20 x 20 matrix.
The device is a ATSAME70Q21B which is Cortex-M7
The compiler is arm branch based on GCC version 13
We are compiling with O3 which has loop-i
On 2021-02-01, 3:19 AM, "Martin Liška" wrote:
EXTERNAL EMAIL: Do not click links or open attachments unless you know the
content is safe
On 1/29/21 3:57 PM, Visda.Vokhshoori--- via Gcc wrote:
>
> Hello,
Hi.
>
> With link time optimi
Hello,
With link time optimization the stack usage information is determined during
local transformation and written to program.ltrans0.ltrans.su. There will be
one .su file for each partition.
All ltrans files, including the .su, are removed unless –save-temps is
indicated.
Although not ob
Hello,
In configuring gcc, there's a check to determine if the linker has support for
STV_Hidden. It determines support by checking for the date in the linker's
version string.
On the other hand, the version string for the linker is constructed without a
date, bfd/Makefile.am recipe for bfdve
Hello,
In GCC documentation, 3.1 Options that Control Optimization: it is indicated
-Os disables alignment of functions, jumps, labels, and loops. However, with
-v -Q passed to the compile step, I see all these options enabled under -Os.
Is this intended behavior, therefore a documentation b
