On 2019-09-19 11:33, Martin Liška wrote:
Hi.
Function reordering has been around for quite some time and a naive
implementation was also part of my diploma thesis some time ago.
Currently, the GCC can reorder function based on first execution, which
happens with PGO and LTO of course. Known
Hello,
The code below causes an internal compiler error in cc1plus (trunk on
x86-64) if it is compiled with -fdump-ipa-cgraph.
int foo () __attribute__ ((target ("default")));
int foo () __attribute__ ((target ("sse4.2")));
__attribute__ ((target ("sse4.2")))
int foo ()
{
return 1;
}
The
On 2016-11-10 13:30, Bin.Cheng wrote:
Hi,
I see the cost problem with your test now. When computing an address
type iv_use with a candidate, the computation consists of two parts,
for computation can be represented by addressing mode, it is done in
memory reference; for computation cannot be
Hello,
I'm facing the following problem related to ivopts. The problem is that
GCC generates a lot of induction variables and as a result there is an
unnecessary increase of stack usage and register pressure.
For instance, for the attached testcase (tc_ivopts.c) GCC generates 26
induction
