From dadcd6ae240e5c2a21b7dc897fa4bea80de7e0e2 Mon Sep 17 00:00:00 2001 From: Dave Eckhardt Date: Wed, 15 May 2019 09:55:15 -0400 Subject: [PATCH] Wording tweaks in comments. --- src/Convert/Enum.hs | 2 +- src/Convert/NamedBlock.hs | 2 +- src/Convert/Struct.hs | 6 +++--- src/Convert/Unique.hs | 6 +++--- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/src/Convert/Enum.hs b/src/Convert/Enum.hs index bfbac7e..e29b2b0 100644 --- a/src/Convert/Enum.hs +++ b/src/Convert/Enum.hs @@ -7,7 +7,7 @@ - modules in which that enum type appears. This is not necessarily foolproof, - as some tools do allow the use of an enum item even if the actual enum type - does not appear in that description. The localparams are explicitly sized to - - match the size of the converted enum type. This conversion only includes enum + - match the size of the converted enum type. This conversion includes only enum - items which are actually used within a given description. - - SystemVerilog allows for enums to have any number of the items' values diff --git a/src/Convert/NamedBlock.hs b/src/Convert/NamedBlock.hs index ebcc473..7714a50 100644 --- a/src/Convert/NamedBlock.hs +++ b/src/Convert/NamedBlock.hs @@ -4,7 +4,7 @@ - Conversion for unnamed blocks with contain data declarations - - SystemVerilog allows data declarations to appear in all blocks, but Verilog - - only allows them to appear in blocks that are named. This conversion gives + - allows them to appear only in blocks that are named. This conversion gives - such blocks a unique name to placate strict Verilog frontends. -} diff --git a/src/Convert/Struct.hs b/src/Convert/Struct.hs index 2c85023..c1ccb64 100644 --- a/src/Convert/Struct.hs +++ b/src/Convert/Struct.hs @@ -179,12 +179,12 @@ packerFnName structTf = val = hash $ show structTf str = tail $ show val --- This is where the magic happens. This is responsible for convertign struct +-- This is where the magic happens. This is responsible for converting struct -- accesses, assignments, and literals, given appropriate information about the -- structs and the current declaration context. The general strategy involves -- looking at the innermost type of a node to convert outer uses of fields, and --- then using the outermost type to figure out the corresping struct definition --- for struct literals that are encountered. +-- then using the outermost type to figure out the corresponding struct +-- definition for struct literals that are encountered. convertAsgn :: Structs -> Types -> (LHS, Expr) -> (LHS, Expr) convertAsgn structs types (lhs, expr) = (lhs', expr') diff --git a/src/Convert/Unique.hs b/src/Convert/Unique.hs index e5793bf..2d46164 100644 --- a/src/Convert/Unique.hs +++ b/src/Convert/Unique.hs @@ -3,9 +3,9 @@ - - Conversion for `unique`, `unique0`, and `priority` - - - This conversion simply drops the keywords, as it is only used for - - optimization. There is no way to force toolchains which don't support the - - keyword to perform such optimization. + - This conversion simply drops the keywords, as it is used only for + - optimization. There is no way to force toolchains which don't support + - the keyword to perform such optimization. -} module Convert.Unique (convert) where