The 1076.6 VHDL subset _was_ expected to be handled by vendors in a consistent way, but no longer after the standard was withdrawn. I've talked to at least one major FPGA vendor who refuses to support some of the things in 1076.6 simply because the standard has been "withdrawn". I would support the idea of having 1076.6 subsumed into the main 1076 standard, so vendors have no excuses not to support any feature mentioned in 1076.6. Best regards, Daniel On 16 May 2014 17:22, Evan Lavelle <eml-vhdl-200x@cyconix.com> wrote: > No. 1076.6 isn't "VHDL"; it's simply a subset of VHDL which synthesis > vendors are expected to handle in a consistent way. It reflects the lowest > common subset of functionality that was expected from synthesis tools at > the specific time that the standard was written. In my opinion, it would be > a major mistake to cast this in stone as part of "VHDL". It is > domain-specific implementation, not language, and is not related to the > core language and its definition. This would be rather like changing the C > or C++ standards to show what Microsoft had achieved in Visual C++ 6.0, for > example. > > We'd also have issues with people believing that VHDL defined concepts > such as "flip flops", clocks, resets, and so on, because "it's in the LRM". > > Finally, some of us will remember that there was a certain amount of > politics in the original 1076.6. With hindsight, this was probably the > start of a very long and slippery path, which has ended with the IEEE > rubber-stamping vendor-defined standards. This is itself, IMO, reason > enough to keep 1076.6 at arm's length from the core language. > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Fri May 16 03:19:31 2014
This archive was generated by hypermail 2.1.8 : Fri May 16 2014 - 03:19:46 PDT