{"push_id":617996946,"size":1,"distinct_size":1,"ref":"refs/heads/release/1.11","head":"34eba66ea7d3540f19a1165746dc205b1e3b91ac","before":"a64f8413b4ce731fb43dc1504aa830c7060d8282","commits":[{"sha":"34eba66ea7d3540f19a1165746dc205b1e3b91ac","author":{"email":"629ff8941cd7d9b2dc921e1e01bf868d31ad3292@acm.org","name":"mppf"},"message":"Merge pull request #1768 from mppf/fix-extern-block-no-clang-included-runtime\n\nBug fix for extern block w/o clang-included runtime\n\nThe --llvm option to compileline changes CHPL_TARGET_PLATFORM in order to use\nclang-included and prevent ABI issues when linking in the runtime. However,\nwhen I originally added that flag I neglected to remember that runClang runs\nboth as an initial step in --llvm compiles but also as a parsing step with\nextern { } blocks even without --llvm. When it's just parsing the extern\nblocks, we shouldn't be changing the CHPL_TARGET_PLATFORM at all. Now we just\nleave out --llvm from the compileline flags if just_parse_filename is set.\n\nBy removing the --llvm option to compileline if we're only parsing extern\nblocks (and not compiling with the LLVM backend), we remove the check\nthat the runtime has been built with clang-included in that case.\n\nTested with test/extern with and without --llvm and with no clang-included runtime without --llvm.\n\nReviewed by @thomasvandoren\n(cherry picked from commit e3a84a63858a493e367366cb04ec854f584e6f2b)","distinct":true,"url":"https://api.github.com/repos/chapel-lang/chapel/commits/34eba66ea7d3540f19a1165746dc205b1e3b91ac"}]}