{"id":36716,"date":"2022-08-09T11:12:39","date_gmt":"2022-08-09T15:12:39","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=36716"},"modified":"2022-08-10T13:38:04","modified_gmt":"2022-08-10T17:38:04","slug":"implementing-parts-of-the-swift-compiler-in-swift","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/08\/09\/implementing-parts-of-the-swift-compiler-in-swift\/","title":{"rendered":"Implementing Parts of the Swift Compiler in Swift"},"content":{"rendered":"

Douglas Gregor<\/a>:<\/p>\n

\n

Here’s a proposed build process for the Swift compiler with Swift code in it:<\/p>\n

    \n
  1. Build C++ bits with the host C++ compiler<\/li>\n
  2. Build mandatory<\/em> Swift bits with the host Swift compiler<\/li>\n
  3. Link a “minimal stage 1\" Swift compiler<\/li>\n
  4. Build optional<\/em> Swift bits with the minimal stage 1 compiler. Note that these bits may not be fully optimized because the stage 1 compiler may lack some optimizer passes.<\/li>\n
  5. Link a “full stage 2” Swift compiler<\/li>\n
  6. Rebuild optional<\/em> Swift bits with the stage 2 compiler.<\/li>\n
  7. Link a “final stage 3” Swift compiler<\/li>\n<\/ol>\n

    […]<\/p>\n

    Personally, I’m excited to open the door to having more Swift code in the compiler, but I want to make sure we’re doing so in a way that doesn’t make it unduly complicated to develop the Swift compiler or port to other host architectures.<\/p>\n<\/blockquote>\n\n

    Previously:<\/p>\n