From 222bd53c2c25d5612f3c56f791fefa3096de7872 Mon Sep 17 00:00:00 2001 From: Brian Gaeke Date: Wed, 24 Sep 2003 18:16:23 +0000 Subject: [PATCH] Update head-of-file comment. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@8699 91177308-0d34-0410-b5e6-96231b3b80d8 --- lib/CodeGen/RegAlloc/PhyRegAlloc.cpp | 11 ++++++++++- lib/Target/SparcV9/RegAlloc/PhyRegAlloc.cpp | 11 ++++++++++- 2 files changed, 20 insertions(+), 2 deletions(-) diff --git a/lib/CodeGen/RegAlloc/PhyRegAlloc.cpp b/lib/CodeGen/RegAlloc/PhyRegAlloc.cpp index 53949a7acfe..0c55219979b 100644 --- a/lib/CodeGen/RegAlloc/PhyRegAlloc.cpp +++ b/lib/CodeGen/RegAlloc/PhyRegAlloc.cpp @@ -1,6 +1,15 @@ //===-- PhyRegAlloc.cpp ---------------------------------------------------===// // -// Register allocation for LLVM. +// Traditional graph-coloring global register allocator currently used +// by the SPARC back-end. +// +// NOTE: This register allocator has some special support +// for the Reoptimizer, such as not saving some registers on calls to +// the first-level instrumentation function. +// +// NOTE 2: This register allocator can save its state in a global +// variable in the module it's working on. This feature is not +// thread-safe; if you have doubts, leave it turned off. // //===----------------------------------------------------------------------===// diff --git a/lib/Target/SparcV9/RegAlloc/PhyRegAlloc.cpp b/lib/Target/SparcV9/RegAlloc/PhyRegAlloc.cpp index 53949a7acfe..0c55219979b 100644 --- a/lib/Target/SparcV9/RegAlloc/PhyRegAlloc.cpp +++ b/lib/Target/SparcV9/RegAlloc/PhyRegAlloc.cpp @@ -1,6 +1,15 @@ //===-- PhyRegAlloc.cpp ---------------------------------------------------===// // -// Register allocation for LLVM. +// Traditional graph-coloring global register allocator currently used +// by the SPARC back-end. +// +// NOTE: This register allocator has some special support +// for the Reoptimizer, such as not saving some registers on calls to +// the first-level instrumentation function. +// +// NOTE 2: This register allocator can save its state in a global +// variable in the module it's working on. This feature is not +// thread-safe; if you have doubts, leave it turned off. // //===----------------------------------------------------------------------===//