On 8/14/23 14:33, Edwin Lu wrote:
On 8/11/2023 6:29 AM, Jeff Law via Gcc-patches wrote:
On 8/10/23 21:45, Palmer Dabbelt wrote:
This seems pretty mechinacial: just scrub through our MDs to check
for any un-typed insns, then add the assert and fix the failures.
You're more than welcome
On 8/11/2023 6:29 AM, Jeff Law via Gcc-patches wrote:
On 8/10/23 21:45, Palmer Dabbelt wrote:
This seems pretty mechinacial: just scrub through our MDs to check
for any un-typed insns, then add the assert and fix the failures.
You're more than welcome to have at it, but LMK if you want
On 8/10/23 21:45, Palmer Dabbelt wrote:
OK, that seems like the way to go. I still think it's likely we'll need
to split up these types more, but that's something we can only deal with
when there's HW that behaves oddly.
Yea, but I think we can fault this in as problematic hardware arrive
On 8/10/23 20:12, Jin Ma wrote:
My fault, I'm very sorry for not replying to the patch follow-up, I just
forgot this :)
No worries. We're tracking it in patchwork and it also overlaps with
some work we had internally at Ventana. So it was trivial to pick it up
once it was clear it'd fall
On Thu, 10 Aug 2023 20:19:02 PDT (-0700), jeffreya...@gmail.com wrote:
On 8/10/23 20:30, Palmer Dabbelt wrote:
Sorry for being lost here, but I'm not sure where TYPE_UNKNOWN comes
from. There's not a whole lot of instances in the code, and they all
seem to be doing something very special.
On 8/10/23 20:30, Palmer Dabbelt wrote:
Sorry for being lost here, but I'm not sure where TYPE_UNKNOWN comes
from. There's not a whole lot of instances in the code, and they all
seem to be doing something very special. Is it just something we didn't
do a '(set_attr "type" ...)' on?
Yup.
On Thu, 10 Aug 2023 19:12:06 PDT (-0700), gcc-patches@gcc.gnu.org wrote:
On 5/29/23 06:46, Jeff Law wrote:
>
>
> On 5/29/23 05:01, Jin Ma wrote:
>> Reference:
>> https://github.com/gcc-mirror/gcc/commit/d0bc0cb66bcb0e6a5a5a31a9e900e8ccc98e34e5
>>
>> RISC-V should also be implemented to handle
> On 5/29/23 06:46, Jeff Law wrote:
> >
> >
> > On 5/29/23 05:01, Jin Ma wrote:
> >> Reference:
> >> https://github.com/gcc-mirror/gcc/commit/d0bc0cb66bcb0e6a5a5a31a9e900e8ccc98e34e5
> >>
> >> RISC-V should also be implemented to handle no_insn patterns for
> >> pipelining.
> >>
> >> gcc/Change
On 5/29/23 06:46, Jeff Law wrote:
On 5/29/23 05:01, Jin Ma wrote:
Reference:
https://github.com/gcc-mirror/gcc/commit/d0bc0cb66bcb0e6a5a5a31a9e900e8ccc98e34e5
RISC-V should also be implemented to handle no_insn patterns for
pipelining.
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_
On 5/29/23 05:01, Jin Ma wrote:
Reference:
https://github.com/gcc-mirror/gcc/commit/d0bc0cb66bcb0e6a5a5a31a9e900e8ccc98e34e5
RISC-V should also be implemented to handle no_insn patterns for pipelining.
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_sched_variable_issue): New functio
Reference:
https://github.com/gcc-mirror/gcc/commit/d0bc0cb66bcb0e6a5a5a31a9e900e8ccc98e34e5
RISC-V should also be implemented to handle no_insn patterns for pipelining.
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_sched_variable_issue): New function.
(TARGET_SCHED_VARIABLE_ISS
11 matches
Mail list logo
