Inline should return failure either (newsize > param_large_function_insns)
OR (newsize > limit). Sometimes newsize is larger than
param_large_function_insns, but smaller than limit, inline doesn't return
failure even if the new function is a large function.
Therefore, param_large_function_insns an
/20200105-1.c: New testcase.
* gcc.c-torture/compile/20200105-2.c: New testcase.
* gcc.c-torture/compile/20200105-3.c: New testcase.
Index: gcc.c-torture/compile/20200105-1.c
===
--- gcc.c-torture/compile/20200105-1.c (nonexistent
Hi,
I noticed there's a costly signed 64-bit division in rtx_cost on x86 as well as
any other target where UNITS_PER_WORD is implemented like TARGET_64BIT ? 8 : 4.
It's also evident that rtx_cost does redundant work for a SET rtx argument.
Obviously the variable named 'factor' rarely exceeds 1, s
Recent platform linkers will no longer accept linking for a target
OS version less than 10.4. Recent SDKs no longer have the libgcc_s
shims used for 10.4 and 10.5. So we need to adjust tests that expect
these. Added some explanation too.
tested on darwin9, darwin16 and darwin18,
applied to main
Hi!
The caching of constexpr calls breaks the following testcase.
The problem is that constexpr calls that allocate from heap something
that they don't deallocate or calls that deallocate something they haven't
allocated aren't stateless for the constexpr context and in each outermost
constexpr ev
On Sat, Jan 4, 2020 at 12:39 PM Jakub Jelinek wrote:
>
> On Sat, Jan 04, 2020 at 12:13:50PM +0100, Uros Bizjak wrote:
> > LGTM, but I wonder if *addcarry_1 gets overmacroized, the insn
> > condition is really hard to comprehend. Perhaps it should be written
> > as a separate pattern for SImode and
