Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

test coverage for cross compiling C code and running it #2058

Open
9 of 48 tasks
andrewrk opened this issue Mar 13, 2019 · 2 comments
Open
9 of 48 tasks

test coverage for cross compiling C code and running it #2058

andrewrk opened this issue Mar 13, 2019 · 2 comments
Labels
contributor friendly This issue is limited in scope and/or knowledge of Zig internals. enhancement Solving this issue will likely involve adding new logic or components to the codebase.
Milestone
0.16.0

Comments

@andrewrk
Copy link
Member

andrewrk commented Mar 13, 2019 •
edited
Loading

Now that we have all these libcs available (See #514), we need test coverage.

  • aarch64_be-linux-gnu
  • aarch64_be-linux-musl
  • aarch64_be-windows-gnu
  • aarch64-linux-gnu
  • aarch64-linux-musl
  • aarch64-windows-gnu
  • armeb-linux-gnueabi
  • armeb-linux-gnueabihf
  • armeb-linux-musleabi
  • armeb-linux-musleabihf
  • armeb-windows-gnu
  • arm-linux-gnueabi
  • arm-linux-gnueabihf (unable to build glibc for target armv8-linux-gnueabihf  #3287)
  • arm-linux-musleabi
  • arm-linux-musleabihf
  • arm-windows-gnu
  • i386-linux-gnu
  • i386-linux-musl
  • i386-windows-gnu
  • mips64el-linux-gnuabi64
  • mips64el-linux-gnuabin32
  • mips64el-linux-musl
  • mips64-linux-gnuabi64
  • mips64-linux-gnuabin32
  • mips64-linux-musl
  • mipsel-linux-gnu
  • mipsel-linux-musl
  • mips-linux-gnu
  • mips-linux-musl
  • powerpc64le-linux-gnu
  • powerpc64le-linux-musl
  • powerpc64-linux-gnu
  • powerpc64-linux-musl
  • powerpc-linux-gnu
  • powerpc-linux-musl
  • riscv32-linux-musl
  • riscv64-linux-gnu
  • riscv64-linux-musl
  • s390x-linux-gnu
  • s390x-linux-musl
  • sparc-linux-gnu
  • sparcv9-linux-gnu
  • x86_64-linux-gnu
  • x86_64-linux-gnux32
  • x86_64-linux-musl
  • x86_64-windows-gnu

The test coverage can be:

  • behavior tests and std lib tests, linking against libc on all these targets, and running with qemu.
  • build hello_world.c against libc on all these targets, and run it with qemu.
@andrewrk andrewrk added the enhancement Solving this issue will likely involve adding new logic or components to the codebase. label Mar 13, 2019
@andrewrk andrewrk added this to the 0.5.0 milestone Mar 13, 2019
@andrewrk andrewrk modified the milestones: 0.5.0, 0.6.0 Apr 30, 2019
@andrewrk
Copy link
Member Author

Rather than an issue that lists all the targets, I'd rather have issues for "Tier 1 support for XYZ", and have "test coverage for libc" be one of the checkboxes.

However, I'll leave this issue open to represent adding a test for building hello_world.c against libc and running it with qemu.

@andrewrk andrewrk changed the title test coverage for all the libc targets test coverage for cross compiling C code for all tier 1 targets Oct 17, 2019
@andrewrk andrewrk changed the title test coverage for cross compiling C code for all tier 1 targets test coverage for cross compiling C code and running it Dec 31, 2019
@andrewrk andrewrk added the contributor friendly This issue is limited in scope and/or knowledge of Zig internals. label Dec 31, 2019
@andrewrk andrewrk modified the milestones: 0.6.0, 0.7.0 Dec 31, 2019
@andrewrk andrewrk modified the milestones: 0.7.0, 0.8.0 Oct 13, 2020
@andrewrk andrewrk modified the milestones: 0.8.0, 0.9.0 Nov 6, 2020
@zhaozg zhaozg mentioned this issue Dec 23, 2020
Open
@andrewrk andrewrk modified the milestones: 0.9.0, 0.10.0 May 19, 2021
@alexrp
Copy link
Contributor

alexrp commented Sep 5, 2024

@andrewrk just checking since this is from 2019: Are we still interested in a C hello world that gets cross-compiled and run with QEMU for each target? Or is our current testing strategy enough?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
contributor friendly This issue is limited in scope and/or knowledge of Zig internals. enhancement Solving this issue will likely involve adding new logic or components to the codebase.
Projects
None yet
Milestone
0.16.0
Development

No branches or pull requests
2 participants
@alexrp @andrewrk