search for: moduleop

...0000 +0300 +++ module-init-tools/Makefile.am 2005-05-23 17:27:26.000000000 +0300 @@ -1,9 +1,9 @@ insmod_SOURCES = insmod.c testing.h lsmod_SOURCES = lsmod.c testing.h -modprobe_SOURCES = modprobe.c zlibsupport.c testing.h zlibsupport.h -rmmod_SOURCES = rmmod.c testing.h -depmod_SOURCES = depmod.c moduleops.c tables.c zlibsupport.c depmod.h moduleops.h tables.h list.h testing.h zlibsupport.h -modinfo_SOURCES = modinfo.c zlibsupport.c testing.h zlibsupport.h +modprobe_SOURCES = modprobe.c zlibsupport.c mod_libc_wrapper.c testing.h zlibsupport.h mod_libc_wrapper.h +rmmod_SOURCES = rmmod.c mod_libc_wra...

...t is being completely missed here. This also requires solving the problem of handling target information in MLIR. But that is a problem which needs to be solved anyway. Using GPU dialect also gives us an opportunity to represent offloading semantics in MLIR. Given the ability to represent multiple ModuleOps and the existence of GPU dialect, couldn't higher level optimizations on offloaded code be done at MLIR level?. The proposed design would lead us to the same problems that we are currently facing in LLVM IR. Also, OpenMP codegen will automatically benefit from the GPU dialect based optimizati...

...e what the problem with "handling target information in MLIR" is > but > whatever design we end up with, we need to know about the target > (triple) in all stages of the pipeline, even if it is just to pass it > down. > > > > Given the ability to represent multiple ModuleOps and the existence of > GPU > > dialect, couldn't higher level optimizations on offloaded code be done at > > MLIR level?. The proposed design would lead us to the same problems that > we > > are currently facing in LLVM IR. > > > > Also, OpenMP codegen will...

...> here. This also requires solving the problem of handling target information > in MLIR. But that is a problem which needs to be solved anyway. Using GPU > dialect also gives us an opportunity to represent offloading semantics in > MLIR. > > Given the ability to represent multiple ModuleOps and the existence of GPU > dialect, couldn't higher level optimizations on offloaded code be done at > MLIR level?. The proposed design would lead us to the same problems that we > are currently facing in LLVM IR. > > Also, OpenMP codegen will automatically benefit from the GPU...

...e problem of handling target information >>> in MLIR. But that is a problem which needs to be solved anyway. Using GPU >>> dialect also gives us an opportunity to represent offloading semantics in >>> MLIR. >>> >>> Given the ability to represent multiple ModuleOps and the existence of >>> GPU dialect, couldn't higher level optimizations on offloaded code be done >>> at MLIR level?. The proposed design would lead us to the same problems that >>> we are currently facing in LLVM IR. >>> >>> Also, OpenMP codegen...

...;>> information in MLIR. But that is a problem which needs to be solved anyway. >>>>> Using GPU dialect also gives us an opportunity to represent offloading >>>>> semantics in MLIR. >>>>> >>>>> Given the ability to represent multiple ModuleOps and the existence of >>>>> GPU dialect, couldn't higher level optimizations on offloaded code be done >>>>> at MLIR level?. The proposed design would lead us to the same problems that >>>>> we are currently facing in LLVM IR. >>>>> &g...