, Yanzhang ; kito.cheng ;
Tobias Burnus
Subject: Re: Re: [PATCH v3] Streamer: Fix out of range memory access of machine
mode
Thanks a lot!
Really appreciate your help ! That's really helpful for RVV (RISC-V vector).
Could you merge your patch after you tested?
T
he.zh...@rivai.ai; rdapp@gmail.com; jeffreya...@gmail.com;
yanzhang.w...@intel.com; kito.ch...@gmail.com; Tobias Burnus
Subject: Re: [PATCH v3] Streamer: Fix out of range memory access of machine mode
Hi!
On 2023-06-29T11:29:57+0200, I wrote:
> On 2023-06-21T15:58:24+0800, Pan Li via Gcc
Hi!
On 2023-06-29T11:29:57+0200, I wrote:
> On 2023-06-21T15:58:24+0800, Pan Li via Gcc-patches
> wrote:
>> We extend the machine mode from 8 to 16 bits already. But there still
>> one placing missing from the streamer. It has one hard coded array
>> for the machine code like size 256.
>>
>> In
gcc-patches@gcc.gnu.org; Robin Dapp;
jeffreya...@gmail.com; yanzhang.w...@intel.com; kito.ch...@gmail.com;
rguent...@suse.de; ja...@redhat.com; Tobias Burnus
Subject: Re: Re: [PATCH v3] Streamer: Fix out of range memory access of machine
mode
Hi!
On 2023-06-29T17:33:14+0800, "juzhe.zh...@r
8)
> FAIL: gcc.target/riscv/rvv/autovec/partial/slp_run-3.c (test for excess
> errors)
That looks like a different issue, though?
Grüße
Thomas
> From: Thomas Schwinge
> Date: 2023-06-29 17:29
> To: Pan Li
> CC: gcc-patches@gcc.gnu.org; juzhe.zh...@rivai.ai; rdapp....@gmail.com;
Subject: Re: [PATCH v3] Streamer: Fix out of range memory access of machine mode
Hi!
On 2023-06-21T15:58:24+0800, Pan Li via Gcc-patches
wrote:
> We extend the machine mode from 8 to 16 bits already. But there still
> one placing missing from the streamer. It has one hard coded array
>
Hi!
On 2023-06-21T15:58:24+0800, Pan Li via Gcc-patches
wrote:
> We extend the machine mode from 8 to 16 bits already. But there still
> one placing missing from the streamer. It has one hard coded array
> for the machine code like size 256.
>
> In the lto pass, we memset the array by MAX_MACHIN
Looks Jivan notices this issue too, cc Jivan for awareness.
> Re: LTO: buffer overflow in lto_output_init_mode_table
> Hi Robbin.
> Thank you for responding.
> I will defer my thread.
> On Thu, Jun 22, 2023 at 3:42 PM Robin Dapp wrote:
>> Hi Jivan,
>>
>> I think Pan is already on this problem.
