Wang Mingyu
8f74a1d164
Changelog: =========== - Update embedded libfabric to fix a build issue on FreeBSD - Fix HIP support for use with AMD GPUs - Fix potential invalid context issue in CUDA memory hooks - Fix GPU fallback path in ch4/ofi for Intel GPU buffers - Fix IPC handle destruction with Level Zero API (Intel GPU) - Fix potential crash in MPI_ISENDRECV with derived datatypes - Fix bug in persistent MPI_GATHER that incorrectly cached buffer contents at init time - Fix memory allocation bug in ROMIO GPFS driver - Fix missing error names in ch4/ofi netmod - Fix potential hang in multi-VCI active message RMA - Fix bug in ch3 large count support with derived datatypes - Fix manpage generation to provide aliases for large-count versions - Fix potential crash in Hydra with long PMI command messages - Fix bug in exit status capture in Hydra when there are multiple processes with non-zero exit - Fix implementation of C/Fortran status conversion functions - Fix implementation of MPI_Type_create_f90_xxx functions Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-oe
This layer depends on:
URI: git://github.com/openembedded/openembedded-core.git branch: master
luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below
pacman -S lib32-gcc-libs lib32-glibc
Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'
You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.
Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.
Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
layer maintainer: Khem Raj raj.khem@gmail.com