Skip to content

LLVM 7.0 tracking issue #50543

Closed
Closed
@alexcrichton

Description

@alexcrichton

I'm opening this to track upgrading to LLVM 7.0. This version of LLVM has not been release and is currently in development on the master branch of LLVM itself, but I'd like to track possible regressions over time and otherwise try to routinely build rustc with LLVM 7 and make sure it keeps working

Reasons to upgrade to LLVM 7

... and likely more coming soon!

Changes required

  • Track down and fix rustdoc panic on x86_64 (and maybe i686?)
  • Track down, report, and pull in fix for codegen failure on Thumb platform
  • fs::tests::realpath_works_tricky is failing on x86_64 MSVC
  • PGO run-make-fulldeps tests failing on x86_64 MSVC
  • Update LLD's @-syntax to always use GNU quoting
  • Serialize custom sections to LLVM IR for wasm instead of manually handling them
  • IR syntax for memcpy/memmove has changed with argument alignments
  • getelementptr syntax has changed with argument alignment
  • Pass --gc-sections to wasm-ld
  • Leverage LLVM for wasm custom sections instead of implementing custom support
  • Pass the --stack-first option to wasm-ld by default
  • The wasm target is now named wasm32-unknown-unkonwn (no trailing -wasm)
  • Pass -O2 to LLD on wasm

Changes hoped for

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions