search for: ebaf94a1

> That's not typically something we'd expose to the end user in any way. > Clang as a compiler should be selecting what it thinks is the fastest > sequence to do some particular job; if it's wrong then that's a bug, > not something to add a command-line flag for. I can't agree with that as a general statement. How is it any different than giving the user the

...ng. For > the issue you are describing, this is more of a question of whether clang > should be emitting the fast flag or not. > > -Matt > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190710/ebaf94a1/attachment.html>