From: Jeremy B. <jer...@em...> - 2020-05-11 08:19:42
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/05/2020 08:38, Cary R. via Iverilog-devel wrote: > I have found a couple things that could be considered enhancements, > but are clearly not supported by the standard. My question is > should we have these enhancements controlled by a flag of some sort > so people can restrict Icarus to only accept what is supported by > the standard? For example pullup/pulldown should only support a > single port. @* is really a single token and the binary ~& and ~| > are not in the standard. There may be more. Is some new strict flag > the correct thing for this? I think @* not being a single token is > a bug and probably should be fixed. I'm personally of the opinion > only standard/commonly supported functionality should be enabled by > default and an extension flag should be used to enable the rest of > this if it is kept. Hi Cary, An important role of free and open source tools is to drive standards, by providing a forum within which new ideas can be tested. Just look at how C and C++ standards emerge from experimental work in GCC and Clang/LLVM. So I should strongly encourage you down this route, with suitable flags to deal with standards enforcement. It might be worth reaching out to over free and open source tools in the space (for example Verilator) to agree some consistency over the flags. And indeed to build consensus by providing support across a range of tools. HTH, Jeremy > This would likely require reworking some of the tests to pull out > the enhancements to have them be in a separate file. > > Thoughts? > > Cary > > > _______________________________________________ Iverilog-devel > mailing list Ive...@li... > https://lists.sourceforge.net/lists/listinfo/iverilog-devel > - -- Cell: +44 (7970) 676050 SkypeID: jeremybennett Twitter: @jeremypbennett Email: jer...@em... Web: www.embecosm.com PGP key: 1024D/BEF58172FB4754E1 2009-03-20 -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQRASGDWqmhRZUfAaPW+9YFy+0dU4QUCXrkDwQAKCRC+9YFy+0dU 4V8dAJ9mxPCpH7KJ5zSDavclm9UGbwSi/wCeKDqk4iy3AfoInSkPpWeqQgqvs1c= =vMiR -----END PGP SIGNATURE----- |