aboutsummaryrefslogtreecommitdiff
path: root/src/codegen
diff options
context:
space:
mode:
authorAndrew Kelley <andrew@ziglang.org>2021-11-30 19:41:14 -0700
committerAndrew Kelley <andrew@ziglang.org>2021-11-30 19:45:08 -0700
commitdd62a6d2e8de522187fd096354e7156cca1821c5 (patch)
treedd87ae2dfd106d7de89f91425377659f1e5f8513 /src/codegen
parentf2608df0fb07811ed2d6d41570d1f9ef9a6cd5d6 (diff)
downloadzig-dd62a6d2e8de522187fd096354e7156cca1821c5.tar.gz
zig-dd62a6d2e8de522187fd096354e7156cca1821c5.zip
AstGen: allow non-string-literal inline assembly for stage1
The end-game for inline assembly is that the syntax is more integrated with zig, and it will not allow string concatenation for the assembler code, for the same reasons that Zig does not have a preprocessor. However, inline assembly in zig right now is lacking for a variety of use cases (take a look at the open issues having to do with inline assembly for example), and being able to use comptime expressions to concatenate text is a workaround that real-world users are exploiting to get by in the short term. This commit keeps "assembly code must use string literal syntax" as a compile error when using stage2, but allows it through when using stage1. I expect to revert this commit after making enough improvements to inline assembly that our real world users' needs are satisfied.
Diffstat (limited to 'src/codegen')
0 files changed, 0 insertions, 0 deletions