search for: csky

...lists.llvm.org>; 尚云海 <yunhai.syh at alibaba-inc.com>; 戎杰杰(无音) <jiejie.rjj at alibaba-inc.com>; 瞿仙淼(杯茶) <xianmiao.qxm at alibaba-inc.com>; 沙钧(钧游) <shajun.sj at alibaba-inc.com>; 耿旗(丛丰) <forrest.gq at alibaba-inc.com> 主　题：Re: [llvm-dev] [RFC] Add a new backend called CSKY It is always exciting to see new targets! Can you give a sense of the community that supports this and the hardware roadmap for this? Are there active plans to develop new C-SKY cores? -Chris On Aug 20, 2020, at 2:10 AM, Zeson via llvm-dev <llvm-dev at lists.llvm.org> wrote: Hi, All. I a...

...- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm64-randconfig-003-20240307 | `-- fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead |-- csky-allmodconfig | |-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg | `-- fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead |-- csky-allyescon...

...arm-allyesconfig | |-- drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and | `-- drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size |-- csky-allmodconfig | |-- drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and | |-- drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size | |--...

..._ldo_ops-defined-but-not-used |-- arm-randconfig-001-20240529 | `-- drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used |-- arm-randconfig-004-20240529 | `-- drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used |-- csky-allmodconfig | |-- drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and | |-- drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size | `--...

..._ops-defined-but-not-used |-- arm64-randconfig-002-20240523 | `-- drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used |-- arm64-randconfig-004-20240523 | `-- drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used |-- csky-allmodconfig | |-- drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and | |-- drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size | `--...

...allnoconfig gcc arm64 defconfig gcc arm64 randconfig-001-20240328 gcc arm64 randconfig-002-20240328 gcc arm64 randconfig-003-20240328 gcc arm64 randconfig-004-20240328 gcc csky allmodconfig gcc csky allnoconfig gcc csky allyesconfig gcc csky defconfig gcc csky randconfig-001-20240328 gcc csky randconfig-0...

...0775 fork/vm: Move common PF_IO_WORKER behavior to new flag > c81cc5819faf kernel: Make io_thread and kthread bit fields > 73e0c116594d kthread: Pass in the thread's name during creation > cf587db2ee02 kernel: Allow a kernel thread's name to be set in copy_process > e0a98139c162 csky: Remove kernel_thread declaration Thanks a lot! Mike could you give it a spin to make sure all is well? -- MST

...already set up a buildbot worker for linux-sparc64 that is being used and another one for linux-m68k is ready and waiting. I will later add one for MIPS (I've got a fairly fast Loongson board) and one for 32-bit PowerPC. > Note that, so far, I've been about the only person reviewing the CSKY patches and have > very little spare bandwidth to do it at the moment. I'd encourage the m68k maintainers > to take a look at it and help out as good community members. All of the back ends in LLVM > would be better if more people reviewed code for back ends other than the one or two...

...s3c6400_defconfig gcc arm s5pv210_defconfig clang arm u8500_defconfig gcc arm64 allyesconfig gcc arm64 defconfig gcc arm64 randconfig-r033-20230704 clang csky alldefconfig gcc csky defconfig gcc csky randconfig-r022-20230703 gcc hexagon randconfig-r033-20230704 clang hexagon randconfig-r041-20230703 clang hexagon randconfig-r0...

...s:write()-has-stream-semantic-safe-to-change-nonseekable_open-stream_open. | |-- mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node | `-- mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node |-- csky-allmodconfig | |-- drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and | |-- drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size | |--...

...ocess around the time it was committed (Jan 2015) * ARC https://lists.llvm.org/pipermail/llvm-dev/2017-August/116268.html "but it would be great to have this in tree" may be vaguely counted as an * VE I cannot find related llvm-dev discussions around the time it was committed (Jan 2020) * CSKY (a stub has been added) https://lists.llvm.org/pipermail/llvm-dev/2020-August/144485.html The closest thing to an approval is the sentence "It is always exciting to see new targets!" Also worth noting that some of the initial review patches have just one or no reviewer on the reviewer li...

...active community of m68k enthusiasts (I'm assuming that, in spite of the title of this thread, we are talking about the 68000, not the 6800), so I expect that the promotion to supported back end should go fairly smoothly. Note that, so far, I've been about the only person reviewing the CSKY patches and have very little spare bandwidth to do it at the moment. I'd encourage the m68k maintainers to take a look at it and help out as good community members. All of the back ends in LLVM would be better if more people reviewed code for back ends other than the one or two that they...

I'm running with CentOS 4.3 and the system was setup originaly with no development system and no kernel sources. I'm trying to get the headers and libraries installed and it is giving me fits. I've followed the suggestions on several threads and tried to yum install gcc, kernel-headers, kernel-devel but I seem to not be able to get /usr/include or use/include/sys packages... don't

...ble because there might be usage sites which rely on the implicit preempt disable. So this needs to be done on a case by case basis and the call sites converted to kmap_local(). Note, that this is only tested on X86 and completely untested on all other architectures (at least it compiles except on csky which does not compile with the newest cross tools from kernel.org independent of this change). The lot is available from git://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git highmem It is based on Peter Zijlstras migrate disable branch which is close to be merged into the tip tree, b...

...ble because there might be usage sites which rely on the implicit preempt disable. So this needs to be done on a case by case basis and the call sites converted to kmap_local(). Note, that this is only tested on X86 and completely untested on all other architectures (at least it compiles except on csky which does not compile with the newest cross tools from kernel.org independent of this change). The lot is available from git://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git highmem It is based on Peter Zijlstras migrate disable branch which is close to be merged into the tip tree, b...

...ble because there might be usage sites which rely on the implicit preempt disable. So this needs to be done on a case by case basis and the call sites converted to kmap_local(). Note, that this is only tested on X86 and completely untested on all other architectures (at least it compiles except on csky which does not compile with the newest cross tools from kernel.org independent of this change). The lot is available from git://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git highmem It is based on Peter Zijlstras migrate disable branch which is close to be merged into the tip tree, b...

As well as the actual patch reviews, has there been official approval that the M68k experimental backend can be added to trunk? I guess we need a "Backend: M68k" bugzilla component - is there anything else? On 13/11/2020 22:41, John Paul Adrian Glaubitz via llvm-dev wrote: > Hello! > > On 11/3/20 6:10 PM, Min-Yih Hsu wrote: >> Just a quick update on the Motorola 6800

...mmp2_defconfig clang arm randconfig-r046-20230731 gcc arm64 allyesconfig gcc arm64 defconfig gcc arm64 randconfig-r003-20230731 gcc arm64 randconfig-r021-20230731 clang csky defconfig gcc hexagon randconfig-r001-20230731 clang hexagon randconfig-r022-20230731 clang hexagon randconfig-r041-20230731 clang hexagon randconfig-r045-20230731 clang i386 a...

...8 +- arch/arm64/kernel/smp.c | 2 +- arch/arm64/kvm/handle_exit.c | 2 +- arch/arm64/kvm/hyp/debug-sr.c | 60 ++++----- arch/arm64/mm/context.c | 2 +- arch/c6x/kernel/signal.c | 5 +- arch/csky/kernel/signal.c | 2 +- arch/h8300/kernel/signal.c | 2 +- arch/hexagon/kernel/module.c | 2 +- arch/hexagon/kernel/signal.c | 2 +- arch/ia64/kernel/crash.c | 2 +- arch/ia64/kernel/module.c...

...8 +- arch/arm64/kernel/smp.c | 2 +- arch/arm64/kvm/handle_exit.c | 2 +- arch/arm64/kvm/hyp/debug-sr.c | 60 ++++----- arch/arm64/mm/context.c | 2 +- arch/c6x/kernel/signal.c | 5 +- arch/csky/kernel/signal.c | 2 +- arch/h8300/kernel/signal.c | 2 +- arch/hexagon/kernel/module.c | 2 +- arch/hexagon/kernel/signal.c | 2 +- arch/ia64/kernel/crash.c | 2 +- arch/ia64/kernel/module.c...