Skip to content

Add test using a target JSON spec file in the CI #401

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.

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

Closed
antoyo opened this issue Dec 21, 2023 · 1 comment · May be fixed by #424
Closed

Add test using a target JSON spec file in the CI #401

antoyo opened this issue Dec 21, 2023 · 1 comment · May be fixed by #424
Labels
good first issue Good for newcomers

Comments

@antoyo
Copy link
Contributor

antoyo commented Dec 21, 2023

The documentation describes how to use a JSON spec file. It would be nice to test this in the CI to make sure it keeps working.

Here's an example m68k-unknown-linux-gnu.json:

{
   "arch": "mips",
   "cpu": "m68k",
   "crt-static-respected": true,
   "data-layout": "E-m:m-p:32:32-i8:8:32-i16:16:32-i64:64-n32-S64",
   "dynamic-linking": true,
   "env": "gnu",
   "executables": true,
   "features": "+fpxx,+nooddspreg",
   "has-elf-tls": true,
   "has-rpath": true,
   "is-builtin": false,
   "llvm-target": "m68k-unknown-linux-gnu",
   "max-atomic-width": 32,
   "os": "linux",
   "position-independent-executables": true,
   "relro-level": "full",
   "target-endian": "big",
   "target-family": [
     "unix"
   ],
   "target-mcount": "_mcount",
   "target-pointer-width": "32"
 }

This file could be added in the examples or tests directory.

@antoyo
Copy link
Contributor Author

antoyo commented Apr 12, 2024

Fixed by antoyo#12.

@antoyo antoyo closed this as completed Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant