> on macOS 11.5.1 with XCode 12.5: What is the best method to work around this > Query from someone who I believe just encountered this trying to build 11.2 (In reply to Matt Thompson from comment #10) more like GAS).įor now I guess we have to wait for a reply, If the result comes back "we intended to do this" then there are a couple of options.ġ) ask them to implement some option to disable this (and we can trigger that option from -gtoggle) Which would mean that the production compiler had the advantage of the additional optimisation - but we could still prove that our code-gen was the same with/without debug.Ģ) We can implement (1) ourselves using the llas driver I wrote - which drives the LLVM backend, but presents command line options like cctools (i.e. > change (i.e to produce better optimised code) or an accidental one. > -without-build-config > I am discussing with OSS folks at Apple whether this is an intentional > (In reply to Richard Biener from comment #5)
(In reply to Iain Sandoe from comment #6)
disable debug comparison in the bootstrap ( -without-build-config ) (re-)install xcode 12.4 command line tools and select them for useĢ. I am discussing with OSS folks at Apple whether this is an intentional change (i.e to produce better optimised code) or an accidental one.ġ. loc directives or presence/absence of Lxxxx local labels between branch and its destination.). However this is not in response to changed command line options (so it is an internal decision in the assembler, probably as a result of detecting either. The code is not actually wrong in either case - it simply looks like branch relaxation has been enabled in one case and not the other. The reason for the fail is that the assembler (clang -cc1as) is assembling branch instructions with differing lengths between the debug and non-debug cases. To rule out compare-debug issues also try > Does it work when you use STAGE1_CFLAGS="-O0" (I think clang defaults to (In reply to Richard Biener from comment #5)
0 kommentar(er)
