shenpeifu / vtr-verilog-to-routing

Automatically exported from code.google.com/p/vtr-verilog-to-routing
0 stars 0 forks source link

Bug in ezxml #21

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
We are not currently using the latest version of ezxml.  There is a bug in the 
version we are using when adding tags out of order.  The code segfaults.

I tested with the latest version of ezxml and it corrected the problem.  

I encountered it using the following architecture snippet:

                <interconnect>
                    <direct name="direct1" input="ble.in" output="soft_logic.in"/>
                    <mux name="mux1" input="soft_logic.out[1:1] soft_logic.out[0:0]" output="ff[0:0].D"/>
                    <mux name="mux2" input="soft_logic.out[0:0] ff[0:0].Q" output="ble.out[0:0]"/>
                    <mux name="mux3" input="soft_logic.out[1:1] ff[0:0].Q" output="ble.out[1:1]"/>
                    <direct name="direct4" input="ble.clk" output="ff[0:0].clk"/>                                       
                </interconnect>

Original issue reported on code.google.com by jeffrey....@gmail.com on 8 May 2012 at 12:46

GoogleCodeExporter commented 9 years ago
To clarify, the bug is due to the fact that the 'direct' and 'mux' types are 
mixed, instead of grouped.  Mixing will not always cause the bug - only certain 
orderings will do so.

This is a known issue in past versions of ezxml.

Original comment by jeffrey....@gmail.com on 8 May 2012 at 12:48

GoogleCodeExporter commented 9 years ago
Actually, I mistakenly thought I tested with the new ezxml.  In fact I did not.

I didn't realize we had modified the ezxml.c file.  Perhaps our modifications 
are the source of the bug.  Diffing the latest version of ezxml with our 
version, I only notice the locations that we have changed.

For now we should just be careful in how we write architecture files.

Original comment by jeffrey....@gmail.com on 8 May 2012 at 6:44

GoogleCodeExporter commented 9 years ago
When I get the newest ezxml, add in the line numbers update, and run, it seg 
faults.  Will probably need to do what Ted Campbell did to fix the numerous 
memory access bugs in ezxml if we want to use the newest version.

Original comment by JasonKai...@gmail.com on 9 May 2012 at 8:23