[Librecores Discussion] [GSoC2017] What are your Verilog coding recommendations?

Stefan Wallentowitz stefan at wallentowitz.de
Tue May 30 17:51:00 CEST 2017

On 30.05.2017 15:25, Philipp Wagner wrote:

>> Just out of curiosity, is there anyone aware of a generic
>> approach/framework to verify coding guidelines? I know many software
>> projects have such things, are they hacked together or something
>> established and reusable? Also giving guidance and not only
>> matched/error would be interesting.
> SpyGlass (now Synopsys) and RealIntent Ascent should be the two major
> ones in this area. I don't think there are open sources solutions apart
> from basic linting as supported by Verilator.

I mean even beyond the linter (while this is a wide field already), what
about source level coding style checkers? With a combination of both one
can apparently cover most of the requirement for example found in oh!


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.librecores.org/pipermail/discussion/attachments/20170530/df76f3b4/attachment.sig>

More information about the Discussion mailing list