On Sun, Jan 14, 2024 at 4:29 PM Ajit Agarwal wrote:
>
> Hello All:
>
> This patch add the vecload pass to replace adjacent memory accesses lxv with
> lxvp
> instructions. This pass is added before ira pass.
>
> vecload pass removes one of the defined adjacent lxv (load) and replace with
> lxvp.
On Fri, Jan 12, 2024 at 6:30 PM Qing Zhao wrote:
>
> Thanks a lot for the reply.
>
> > On Jan 12, 2024, at 11:28 AM, Richard Biener
> > wrote:
> >
> >
> >
> >> Am 12.01.2024 um 16:55 schrieb Qing Zhao :
> >>
> >> Hi,
> >>
> >> I have some questions on using the utility routine “unshare_expr”:
On Sun, Jan 14, 2024 at 8:32 PM Roger Sayle wrote:
>
>
> This patch fixes three of the four unexpected failures that I'm seeing
> in the gcc testsuite on x86_64-pc-linux-gnu. The three FAILs are:
> FAIL: gcc.c-torture/execute/fprintf-2.c -O3 -g (test for excess errors)
> FAIL:
Compile tested for the ia64-elf target; bootstrap and regtest running
on x86_64-redhat-linux. Ok for trunk when successful?
ia64-elf build fails with the following warning:
[all 2024-01-12 16:32:34] ../../gcc/gcc/config/ia64/ia64.cc:3889:59:
error: unused parameter 'decl'
Hello All:
Following performance gains for spec2017 FP benchmarks.
554.roms_r 16% gains
544.nab_r 9.98% gains
521.wrf_r 6.89% gains.
Thanks & Regards
Ajit
On 14/01/24 8:55 pm, Ajit Agarwal wrote:
> Hello All:
>
> This patch add the vecload pass to replace adjacent memory accesses lxv with
This patch adds C intrinsics for Bitmanip Extension.
RISCV_BUILTIN_NO_PREFIX is a new riscv_builtin_description like RISCV_BUILTIN.
But it uses CODE_FOR_##INSN rather than CODE_FOR_riscv_##INSN.
Changed orcb, clmul, brev8 pattern's mode form X to GPR because orcbsi,
clmul_si,
brev8_si are both
This patch adds C intrinsics for Scalar Crypto Extension.
gcc/ChangeLog:
* config.gcc: Include riscv_crypto.h.
* config/riscv/riscv_crypto.h: New file.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/scalar_crypto_intrinsic-32.c: New test.
*
On Mon, 15 Jan 2024, Jakub Jelinek wrote:
> Hi!
>
> The INTEGER_CST code uses the remainder bits in computations whether to use
> whole constant or just part of it and extend it at runtime, and furthermore
> uses it to avoid using all bits even when using the (almost) whole constant.
> The
On Sat, 13 Jan 2024, Jakub Jelinek wrote:
> Hi!
>
> As the testcase shows, the INTEGER_CST handling in handle_operand_addr
> (i.e. what is used when passing address of an integer to a bitint library
> routine) wasn't correct. If the minimum precision to represent an
> INTEGER_CST is smaller or
The serials patch provides a mapping from the RV intrinsics to the builtin
names.
There are some duplicates testsuites between intrinsic and built-in function.
Remove the Scalar Bitmanip and Scalar Crypto Built-In function testsuites
that will be included in the intrinsic functions.
Hi!
The INTEGER_CST code uses the remainder bits in computations whether to use
whole constant or just part of it and extend it at runtime, and furthermore
uses it to avoid using all bits even when using the (almost) whole constant.
The problem is that the prec % (2 * limb_prec) computation it
Update v3 -> v4:
1.Typo fix.
2.Only test *intrinsic-32 on rv32 and *intrinsic-64 on rv64.
3.Update Copyright year to 2024.
Update v2 -> v3:
1. Change pattern mode form X to GPR in orcb, clmul, and brev8.
2. Add emulated testsuite.
3. Removed duplicate testsuite between built-in and
> Okay, so, the "unsharing everything” is done automatically by the compiler
> before gimplification?
See the blurb at gimplify.cc:835 and below about this.
--
Eric Botcazou
Hi Kewen,
在 2024/1/15 14:16, Kewen.Lin 写道:
> Considering it's stage 4 now and the impact of this patch, let's defer
> this to next stage 1, if possible could you organize the above changes
> into patches:
>
> 1) Refactor expand_compare_loop by splitting into two functions without
>any
101 - 114 of 114 matches
Mail list logo