Fix some comments

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@56460 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Mikhail Glushenkov 2008-09-22 20:46:44 +00:00
parent fdee954623
commit d92f2e01fc
2 changed files with 4 additions and 14 deletions

View File

@ -1,4 +1,4 @@
//===- Graph.td - LLVMCC toolchain descriptions ------------*- tablegen -*-===//
//===- Graph.td - LLVMC2 toolchain descriptions ------------*- tablegen -*-===//
//
// The LLVM Compiler Infrastructure
//
@ -7,7 +7,7 @@
//
//===----------------------------------------------------------------------===//
//
// This file contains compilation graph description used by llvmcc.
// This file contains compilation graph description used by llvmc2.
//
//===----------------------------------------------------------------------===//

View File

@ -1,4 +1,4 @@
//===- Tools.td - Tools description for the LLVMCC --------*- tablegen -*-===//
//===- Tools.td - Tools description for LLVMC2 -------------*- tablegen -*-===//
//
// The LLVM Compiler Infrastructure
//
@ -7,20 +7,10 @@
//
//===----------------------------------------------------------------------===//
//
// This file contains descriptions of the various build tools run by llvmcc.
// This file contains descriptions of the various build tools run by llvmc2.
//
//===----------------------------------------------------------------------===//
// TOTHINK: Open issue: should we use DAG lists in Tool specifications
// or change to something like
// def LLVMGccC : < Tool<
// [ InLanguage<"c">,
// PrefixListOption<"Wl", [UnpackValues, PropertyName<Arg>, ...]>
// ...] ?
// DAG lists look more aesthetically pleasing to me.
def llvm_gcc_c : Tool<
[(in_language "c"),
(out_language "llvm-bitcode"),