From a39bf3da7b13baff1326acbd25d69183ff00e11e Mon Sep 17 00:00:00 2001 From: Reid Spencer Date: Tue, 10 Aug 2004 16:38:18 +0000 Subject: [PATCH] Fixed some spellos and grammaros. llvm-svn: 15610 --- llvm/docs/CommandLine.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/llvm/docs/CommandLine.html b/llvm/docs/CommandLine.html index 735337501910..aea3ec843c0e 100644 --- a/llvm/docs/CommandLine.html +++ b/llvm/docs/CommandLine.html @@ -458,10 +458,10 @@ things it doesn't know about, like enums or 'int*'s?

The answer is that it uses a table driven generic parser (unless you specify your own parser, as described in the Extension -Guide). This parser maps literal strings to whatever type is required, are +Guide). This parser maps literal strings to whatever type is required, and requires you to tell it what this mapping should be.

-

Lets say that we would like to add four optimizations levels to our +

Lets say that we would like to add four optimization levels to our optimizer, using the standard flags "-g", "-O0", "-O1", and "-O2". We could easily implement this with boolean options like above, but there are several problems with this strategy: