Skip to content

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

Closed
@antoyo

Description

@antoyo

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy