diff options
| author | tromey <tromey@138bc75d-0d04-0410-961f-82ee72b054a4> | 2005-03-07 20:16:25 +0000 |
|---|---|---|
| committer | tromey <tromey@138bc75d-0d04-0410-961f-82ee72b054a4> | 2005-03-07 20:16:25 +0000 |
| commit | f280d70a0d905342f64209a374fb28d5ce127792 (patch) | |
| tree | 2ec4abec89652053f890da26b60bf7b63d1158b9 /gcc/java | |
| parent | 395b124c1571b138b05cf889d37624dcc15f2d16 (diff) | |
| download | gcc-f280d70a0d905342f64209a374fb28d5ce127792.tar.gz | |
gcc/java:
* gcj.texi (Invoking gcj-dbtool): Document '-f'.
libjava:
* gnu/gcj/tools/gcj_dbtool/Main.java (main): Recognize '-f'.
(usage): Document '-f'.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@96041 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/java')
| -rw-r--r-- | gcc/java/ChangeLog | 4 | ||||
| -rw-r--r-- | gcc/java/gcj.texi | 8 |
2 files changed, 10 insertions, 2 deletions
diff --git a/gcc/java/ChangeLog b/gcc/java/ChangeLog index 248627a6330..a03c6605091 100644 --- a/gcc/java/ChangeLog +++ b/gcc/java/ChangeLog @@ -1,3 +1,7 @@ +2005-03-07 Tom Tromey <tromey@redhat.com> + + * gcj.texi (Invoking gcj-dbtool): Document '-f'. + 2005-03-06 Kazu Hirata <kazu@cs.umass.edu> * jcf-dump.c, jcf-io.c, jcf-reader.c, lang.c, parse.h, diff --git a/gcc/java/gcj.texi b/gcc/java/gcj.texi index b270b6fbbcf..227c230b9d7 100644 --- a/gcc/java/gcj.texi +++ b/gcc/java/gcj.texi @@ -990,7 +990,8 @@ Each time a class is initialized, print a short message on standard error. @c man begin SYNOPSIS gcj-dbtool gcj-dbtool @option{OPTION} @var{DBFILE} [@option{MORE}] @dots{} -gcj-dbtool [@option{-n}] [@option{-a}] [@option{-t}] [@option{-l}] +gcj-dbtool [@option{-n}] [@option{-a}] [@option{-f}] + [@option{-t}] [@option{-l}] [@option{-v}] [@option{--version}] [@option{--help}] @c man end @@ -1027,11 +1028,14 @@ you can choose a larger initial size if desired. The default size is 32,749. @item -a @var{DBFILE} @var{JARFILE} @var{LIB} +@itemx -f @var{DBFILE} @var{JARFILE} @var{LIB} This adds a jar file to the database. For each class file in the jar, a cryptographic signature of the bytecode representation of the class is recorded in the database. At runtime, a class is looked up by its signature and the compiled form of the class is looked for in the -corresponding shared library. +corresponding shared library. The @option{-a} option will verify +that @var{LIB} exists before adding it to the database; @option{-f} +skips this check. @item -t @var{DBFILE} Test a database. |