Re: [myhdl-list] fixbv to current version of myhdl

[Jose M. G. C. <ch...@gm...>]

Dear Christopher,

I agree that I have not followed the standard approach. The reason has been that I needed thinks for yesterday, and I needed it to run quickly. I needed to move from a previous platform to an open one, and I saw myhdl as a good approach. I also needed fixed point, but the fixbv approach, which is equivalent to the one provided in opencores did not fulfil my requirements, as I needed a resize.

Basically I needed the VHDL fixed package on myhdl. One thing bring to another, and the small package has become a little monster that has required a lot of changes, including the converter code.

Sincerely, for me it would be perfect to help you with the fixbv, and provide to it the same functionality as the VHDL fixed. But in my opinion, this will need also to modify intbv and create helping functions in Verilog for rounding, saturate or, in other words, resizing, if not the code will become a mess in Verilog. Just look at the code generated by the test in VHDL with the helping functions that have been already added, and it is still a little mess.

But please, check the code and give it a try. I am sure you will find some aspects to improve and others that could be useful, and we can try to find a way to have a powerful fixed point type in myhdl. Moreover, this changes shall allow to add a floating point type afterwards.

Best,

Jose M.



> El 02/05/2015, a las 17:48, Christopher Felton <chr...@gm...> escribió:
> 
>> On 5/1/15 4:16 PM, Jose M. Gomez Cama wrote:
>> Dear all,
>> 
>> I have created a series of new types that allow to work with fixed point
>> and is compatible with the fixed point from VHDL. I am still working on
>> it, but it is presently compatible with GHDL, vcom and symplify.
>> 
>> I have not published it before because it uses a new base class,
>> bitarray. I have also created classes for the signed and unsigned types.
>> It still requires some tunning, because it is slower than intbv, as it
>> is fully object oriented, which adds some overhead.
>> 
>> I do not know how to proceed as the number of changes is quite large.
>> And I wanted to discuss it before hand, but as I saw this mail, I
>> thought it could be useful.
>> 
>> In brief, the package is in git, under the user jmgc, fork numeric.
> 
> This approach sounds like it would be an additional pkg
> bolt on and not part of myhdl?
> 
>> 
>> And Jan, if you think it can be added to myhdl, please, tell me how I
>> shall proceed.
> 
> Typically, for a new feature the best approach is to
> follow the development guidelines, which include creating
> a MEP and discussing on the mailing-list:
> 
> http://dev.myhdl.org/guide/guide.html#contributing-changes
> http://dev.myhdl.org/meps/mep-001.html
> 
> Regards,
> Chris
> 
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> myhdl-list mailing list
> myh...@li...
> https://lists.sourceforge.net/lists/listinfo/myhdl-list