On Thu, Jan 28, 2010 at 05:14:59PM +0100, Martin Zenzes wrote:
> Hi!
> 
> I'm running into some trouble trying to include an IP-Core "FIR-Compiler
> 4.0" from Xilinx 10.4 into an existing ghdl-Projekt. Maybe someone is
> able to help me?

[...]

> But I'm getting some errors during analysing the Xilinx-vhd files:
> -------------------------------------------------------------
> /opt/xilinx/10.1/ISE/vhdl/src/XilinxCoreLib/fir_compiler_v4_0.vhd:217:36: 
> constant "round_mode" is not visible here
> /opt/xilinx/10.1/ISE/vhdl/src/XilinxCoreLib/fir_compiler_v4_0.vhd:220:41: 
> constant "round_mode" is not visible here
> /opt/xilinx/10.1/ISE/vhdl/src/XilinxCoreLib/fir_compiler_v4_0.vhd:222:41: 
> constant "round_mode" is not visible here
> /opt/xilinx/10.1/ISE/vhdl/src/XilinxCoreLib/fir_compiler_v4_0.vhd:224:39: 
> constant "round_mode" is not visible here
> -------------------------------------------------------------

Yes, Xilinx uses invalid vhdl syntax.

> I tried to comment-out the complete declaration of the named constant.
> But I have to admit that I didn't dig any deeper into the code... Now,
> ghdl runs through (with a whole bunch of warnings), but crashes right
> afterwards:
> -------------------------------------------------------------
> ...
> analyze fir_compiler_v4_0.vhd
> fir_compiler_v4_0.vhd:119:1:warning: no default binding for
> instantiation of component "wrapped_fir_compiler_v4_0"
> fir_compiler_v4_0.vhd:55:11:warning: visible declaration for
> wrapped_fir_compiler_v4_0 is component "wrapped_fir_compiler_v4_0"
> fir_compiler_v4_0.vhd:55:11:warning: no entity
> "wrapped_fir_compiler_v4_0" in library "work"
> analyze byte2file.vhd
> analyze 
> /opt/xilinx/10.1/ISE/vhdl/src/XilinxCoreLib/fir_compiler_v4_0_mac_fir.vhd
> 
> ******************** GHDL Bug occured ****************************
> Please report this bug on http://gna.org/projects/ghdl

[...]

Looks like you have found a bug in GHDL.  Could you try with GHDL 0.29 ?
If the bug is still there, could you send byte2file.vhd to me ?


> Now I don't know whether to blame
> - me for providing uncomplete declaration of my *.vhd-files
> - me for wrong editing of Xilinx-code
> - ghdl for crashing
> - Xilinx for writing and providing ugly and unportable code...

I think the last two ;-)

Tristan.

_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss

Reply via email to