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.

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

Use more information from rustc's target spec #1249

Open
1 of 15 tasks
madsmtm opened this issue Oct 31, 2024 · 0 comments
Open
1 of 15 tasks

Use more information from rustc's target spec #1249

madsmtm opened this issue Oct 31, 2024 · 0 comments

Comments

@madsmtm
Copy link
Contributor

madsmtm commented Oct 31, 2024

There's a lot more useful information exposed in rustc's target spec that cc could use after #1225. Opening this issue to track the progress on using those.

Specifically:

  • llvm-target: Use rustc's knowledge of LLVM/Clang target triples #1252
  • llvm-abiname
  • target-endian
  • linker
  • pre-link-objects/post-link-objects/pre-link-objects-fallback/crt-static-allows-dylibs/etc. for better -Clink-self-contained?
  • link-env/link-env-remove
  • cpu? See also Pass target-cpu to C compilers #268
  • dynamic-linking (for diagnostics?)
  • frame-pointer
  • default-dwarf-version
  • position-independent-executables/static-position-independent-executables
  • panic-strategy (for -fno-exceptions)
  • eh-frame-header?
  • Atomics (cfg!(target_has_atomic = "..."))?
  • Whether thread locals are available (cfg!(target_thread_local))?

Note that we still have to implement fallbacks for each of these for custom target specs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant