en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Frontend/ir-support-errors.ll#925213b0 Add 'not' to commands that are expected to fail.This is at least good documentation, but also opens the possibility ofusing pipefail.llvm-svn: 185652 List of files: /llvm-project-15.0.7/clang/test/Frontend/ir-support-errors.ll Thu, 04 Jul 2013 16:16:58 +0000 Rafael Espindola <rafael.espindola@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Frontend/ir-support-errors.ll#778b8b84 Escape % in diagnostic message when compiling LLVM IR.% is a common character in IR so we'd crash on almost any malformed IR. Thediagnostic formatter expects a formatting directive when it sees an unescaped %.llvm-svn: 152956 List of files: /llvm-project-15.0.7/clang/test/Frontend/ir-support-errors.ll Fri, 16 Mar 2012 22:31:42 +0000 Benjamin Kramer <benny.kra@googlemail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Frontend/ir-support-errors.ll#6f8362c6 Frontend: Add CodeGenAction support for handling LLVM IR. - This magically enables using 'clang -cc1' as a replacement for most of 'llvm-as', 'llvm-dis', 'llc' and 'opt' functionality.For example, 'llvm-as' is: $ clang -cc1 -emit-llvm-bc FOO.ll -o FOO.bcand 'llvm-dis' is: $ clang -cc1 -emit-llvm FOO.bc -o -and 'opt' is, e.g.: $ clang -cc1 -emit-llvm -O3 -o FOO.opt.ll FOO.lland 'llc' is, e.g.: $ clang -cc1 -S -o - FOO.llThe nice thing about using the backend tools this way is that they are guaranteed to exactly match how the compiler generates code (for example, setting the same backend options).llvm-svn: 105583 List of files: /llvm-project-15.0.7/clang/test/Frontend/ir-support-errors.ll Mon, 07 Jun 2010 23:27:59 +0000 Daniel Dunbar <daniel@zuster.org>