Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 20 08:07
    Astiolo commented #1954
  • Jan 20 06:39
    tgingold commented #1954
  • Jan 20 06:37
    tgingold closed #1953
  • Jan 20 06:37
    tgingold commented #1953
  • Jan 20 00:57
    Astiolo commented #1954
  • Jan 19 23:34
    umarcor commented #1954
  • Jan 19 23:29
    Astiolo opened #1954
  • Jan 19 16:00
    Scafir opened #1953
  • Jan 18 19:52
    tgingold commented #1952
  • Jan 18 19:40
    seijikun commented #1952
  • Jan 18 17:17
    tgingold commented #1952
  • Jan 18 15:47
    seijikun commented #1952
  • Jan 18 15:33
    umarcor commented #1952
  • Jan 18 15:04
    seijikun commented #1952
  • Jan 18 14:56
    seijikun commented #1952
  • Jan 18 14:53
    Paebbels labeled #1952
  • Jan 18 14:53
    Paebbels labeled #1952
  • Jan 18 14:53
    Paebbels commented #1952
  • Jan 18 13:56
    seijikun edited #1952
  • Jan 18 13:35
    seijikun edited #1952
Those three examples are based on Makefiles. However, each of them uses an slightly different style and source organisation.
Sammy Lin
@bkzshabbaz
I am using the "components". I'm also using the EHXPLLL component, and it's not complaining about that.
I brought this up in the ulx3s gitter chat and they mentioned the oddrx1f component isn't capitalized.
@gatecat
It should be in capitals
I suspect there is some kind of GHDL issue going on here but don't know how to fix it
Unai Martinez-Corral
@umarcor
@bkzshabbaz if that is the case, please provide a MWE which we can execute and test. There have been some other issues related to lower/upper. Strictly, VHDL is not case sensitive, so it should not be relevant.
Sammy Lin
@bkzshabbaz
Will do. Does the rest of the toolchain's case sensitivity matter?
Unai Martinez-Corral
@umarcor
That might be the case. Maybe GHDL does not have a problem with it, but Yosys or nextpnr do.
Sammy Lin
@bkzshabbaz
Should I submit a Github issue?
Unai Martinez-Corral
@umarcor
Yes, please. You can add the MWE to some branch in some repo of yours, tho. You don't need to copy the sources to the body of the issue if you don't want to.
See ghdl/ghdl#1682. Not exactly the same, but also related to upper casing between GHDL and one specific variant of yosys.
Sammy Lin
@bkzshabbaz
Yup, exactly what I was thinking about.
Unai Martinez-Corral
@umarcor
Note that in that case the "request" was to "always emit uppercase" to the backend.
However, it could be handled by an specific option in yosys.
Sammy Lin
@bkzshabbaz
attrmap -tocase ODDRX1F?
Unai Martinez-Corral
@umarcor
Yeah, that might be. I don't know where in the pipeline you need to put it, tho. Maybe after 'ghdl' and before 'synth_ecp5'?
Sammy Lin
@bkzshabbaz
Thinking the same thing.
Sammy Lin
@bkzshabbaz
Not sure if attrmap is working, since this isn't an attribute?
Will get a MWE branch up soon.
Vitaly Konovalov
@arnfol

Hi everyone!
I am trying to install ghdl-ls on my WSL Ubuntu 18.04. Everything looks fine, but when I am calling ghdl-ls I got following:

Traceback (most recent call last):
  File "/home/arnfol/anaconda3/bin/ghdl-ls", line 5, in <module>
    from pyGHDL.cli.lsp import main
  File "/home/arnfol/anaconda3/lib/python3.8/site-packages/pyGHDL/cli/lsp.py", line 44, in <module>
    import pyGHDL.libghdl as libghdl
  File "/home/arnfol/anaconda3/lib/python3.8/site-packages/pyGHDL/libghdl/__init__.py", line 149, in <module>
    libghdl = _initialize()
  File "/home/arnfol/anaconda3/lib/python3.8/site-packages/pyGHDL/libghdl/__init__.py", line 131, in _initialize
    _libghdl_path = _get_libghdl_path()
  File "/home/arnfol/anaconda3/lib/python3.8/site-packages/pyGHDL/libghdl/__init__.py", line 126, in _get_libghdl_path
    raise Exception("Cannot find libghdl {}".format(basename))
Exception: Cannot find libghdl libghdl-2_0_0_dev.so

Here is my installation script:

#!/usr/bin/env bash

sudo apt-get install -y libz-dev
sudo apt-get install -y gcc gnat

# get & install GHDL
git clone https://github.com/ghdl/ghdl.git
cd ghdl
mkdir build && cd build
../configure --prefix=/opt/ghdl
make && make install

# install PyGHDL
cd ..
pip3 install .

What am I doing wrong?

found the libghdl in /opt/ghdl/lib/libghdl-2_0_0_dev.so and here is my ghdl --dispconfig output:
command_name: /opt/ghdl/bin/ghdl
command line prefix (--PREFIX): (not set)
environment prefix (GHDL_PREFIX): (not set)
exec prefix (from program name): /opt/ghdl

library prefix: /opt/ghdl/lib/ghdl
library directory: /opt/ghdl/lib/ghdl
default library paths:
 /opt/ghdl/lib/ghdl/ieee/v93/
 /opt/ghdl/lib/ghdl/
Vitaly Konovalov
@arnfol
however I can't understand what's wrong here)
Unai Martinez-Corral
@umarcor
/opt/ghdl/lib is not an standard location for libraries. You need to specify it through some envvar.
Locate the directory where the shared library is installed.
Search order:
  1. GHDL_PREFIX - directory (prefix) of the vhdl libraries.
  2. VUNIT_GHDL_PATH - path of the ghdl binary when using VUnit.
  3. GHDL - name of, or path to the ghdl binary.
  4. Try within libghdl/ Python installation.
  5. Try when running from the build directory.
Vitaly Konovalov
@arnfol
do I need to specify it for the installation process only?
Running GHDL_PREFIX=/opt/ghdl/lib/ ghdl-ls cause the same error
Unai Martinez-Corral
@umarcor
What's the location of libghdl-2_0_0_dev.so?
Did you try GHDL=/opt/ghdl/bin/ghdl ghdl-ls?
I think that GHDL_PREFIX needs to point to a subdir of lib: GHDL_PREFIX=/opt/ghdl/lib/ghdl ghdl-ls
Kaleb Barrett
@ktbarrett
Does GHDL support VHDL-2019 Interfaces? Is there any documentation on what language features are supported/missing in each language revision? Something like this maybe?
I ran into type-generic entities not being supported last night =/ and a coworker is asking about interfaces.
Unai Martinez-Corral
@umarcor
@ktbarret, interfaces are not supported and generic types are supported mostly for the fixed and float packages, so not for entities.
Kaleb Barrett
@ktbarrett
That's unfortunate. Is there a timeline on when features will be implemented? Is there some general plan available for GHDL's future development?
Unai Martinez-Corral
@umarcor
Not at all. All the known info is whatever you can get by watching the repo and inspecting the commits that Tristan pushes. There is no further roadmap other than that. There is https://github.com/ghdl/ghdl/wiki as very general guidelines, but most of the features are added by surprise.
The same applies to bug fixes. If Tristan replies to an issue saying he is looking at it, you might expect a fix in a few hours/days. Otherwise, it can take weeks or months.
I know that Tristan wants to support generics, external names and unconstrained arrays, which are the three most relevant missing VHDL 2008 features. However, those are complex, because the elaboration model is very different from previous revisions. He was sidetracked with synthesis 2-3 years ago, which I believe we are all very thankful about. Lately, there have been several comments about Rust, JIT (deprecating GCC), supporting merging multiple revisions, etc. I believe all of those are small steps towards being able to implement 2008 and 2019 features properly. Nonetheless, that won't be quick.
With regard to interfaces, as valuable as I think they are, I would expect them to be added after the main 2008 features are done. Interfaces are more useful with generic types and unconstrained arrays.
Unai Martinez-Corral
@umarcor
Other than that, as you might already know, these last months we've been talking about proposing some kind of "VHDL Foundation" in order to be able to handle funds/donations and hopefully hire Tristan partially (through an agreement with his current employer). That is the very main priority we all agree on: having an open source implementation of the language which can be used as a reference. Once GHDL supports 2008 and 2019, it might be feasible to implement upcoming LCS after they are approved but before the standard is released. Yet, that's something that no single human can do. We can neither ask nor allow Tristan to do that himself. We need to scale.
The main problem is who is going/willing to manage that. I am "a child" and I don't have the economical stability for doing that. Someone or a group of people needs to step ahead, which "the community" accepts as legit for making good use of whichever resources are gathered in the name of "improving the open source VHDL ecosystem (tooling, tests, libraries, learning/teaching material...)".
Note that the "VHDL Foundation" is just a concept. In practice, it would probably be some group in an existing foundation. However, it needs not to be IEEE, because there would be conflicts of interest.
Unai Martinez-Corral
@umarcor
In the VASG meeting before the last one, I commented this with @JimLewis and @Paebbels. I had been mostly thinking about it from a EU perspective, and discussing it with @LarsAsplund. However, EU funds might be limited to EU citizens. Jim might try to replicate the same in the US. It would be nice if you, @marlonjames, @GlenNicholls and others could somehow coordinate.
For now, I created a private repository in my namespace in GitLab, where I'm gathering all the references and ideas in this regard. It's a pot-pourri yet, and there might be some sensible references, so I don't want to make it public. However, I have no problem for sharing it with you or others who are interested.
Jim Lewis
@JimLewis
@umarcor GHDLs support for generics on packages is good. GHDLs support for unconstrained arrays on ports is getting better. I have everything in OSVVM running.
Unai Martinez-Corral
@umarcor
@JimLewis it is, but we cannot tell at what extent it works. Tristan did not sit down and say "I will analyse all these cases and ensure that they work". Note that Kaleb asked about generics in entities, not packages. I vaguely recall that Tristan didn't find it prioritary.
Jim Lewis
@JimLewis
If I could set the priorities, I would put 2019 interfaces ahead of type generics on entities. I would put 2019 interfaces on a similar priority to external names. Although for existing code, I would say external names is higher priority.
@umarcor I don't find type generics on entities a priority either.
When I have time, I will unwind my work arounds in OSVVM and submit further test cases for unconstrained elements of composites.
Kaleb Barrett
@ktbarrett
Type generic FIFO entities are a huge deal. No more need to manually type convert and pack everything into a logic vector.
Unai Martinez-Corral
@umarcor
Here it is!
So, Tristan didn't make any assessment. He just asked about it.