mirror of
https://git.savannah.gnu.org/git/gperf.git
synced 2025-12-02 13:09:22 +00:00
Introduce new alpha_inc pass, to avoid artificial duplicates.
This commit is contained in:
@@ -993,7 +993,7 @@ through a search that minimizes the number of byte positions.
|
||||
@itemx --duplicates
|
||||
@cindex Duplicates
|
||||
Handle keywords whose selected byte sets hash to duplicate values.
|
||||
Duplicate hash values can occur for three reasons:
|
||||
Duplicate hash values can occur for two reasons:
|
||||
|
||||
@itemize @bullet
|
||||
@item
|
||||
@@ -1003,15 +1003,6 @@ However, frequently only a very small number of duplicates occur, and
|
||||
the majority of keywords still require one probe into the table. To
|
||||
overcome this problem, the option @samp{-m 50} should be used.
|
||||
|
||||
@item
|
||||
Since the @code{gperf} generated hash function treats the bytes at
|
||||
different byte positions with equal weight, keywords that are permutations
|
||||
of each other can lead to the same hash function value if they are not
|
||||
disambiguated by the set of selected byte positions. Sometimes even this
|
||||
is not possible; for example, the keyword set @{"xy", "yx", "xz", "zx"@}
|
||||
will always lead to duplicates, regardless how the selected byte positions
|
||||
are chosen. You can use the option @samp{-D} to handle this rare case.
|
||||
|
||||
@item
|
||||
Sometimes a set of keywords may have the same names, but possess different
|
||||
attributes. With the -D option @code{gperf} treats all these keywords as
|
||||
|
||||
Reference in New Issue
Block a user