Hi,

I try to compile the tip but I get the following linker errors:

./ortho_code-x86-abi.o: In function `ortho_code__x86__abi__link_intrinsics':
/home/endre/Prg/ghdl/src/ortho/mcode/ortho_code-x86-abi.adb:773: undefined
reference to `__muldi3'
/home/endre/Prg/ghdl/src/ortho/mcode/ortho_code-x86-abi.adb:777: undefined
reference to `__divdi3'
/home/endre/Prg/ghdl/src/ortho/mcode/ortho_code-x86-abi.adb:781: undefined
reference to `__moddi3'
collect2: error: ld returned 1 exit status
gnatlink: error when calling /usr/bin/gcc-4.8
gnatmake: *** link failed.

I am using gnat-4.8, is that okay?
What libs should I install to satisfy the linker?

Thanks,
Endre

On Sun, Mar 1, 2015 at 7:24 AM, Tristan Gingold <[email protected]> wrote:

> On 28/02/15 19:11, Endre Bak wrote:
>
>> Hi,
>>
>> Here are the files.
>> I have also included my results here: MyConsoleOutput.txt
>>   MyGhdlVersion.txt  MyGtkWaveOutput.png
>>
>
> Hello,
>
> thank you for the reproducer.  The simulation is correct with
> the tip version, so the bug has already been fixed.
>
> I think the issue was in fact in the VCD dumper, but I may
> remember incorrectly.
>
> You may simply build the tip version by yourself and use it.
>
> Thanks!
> Tristan.
>
>
>> You can view the waves by executing:
>>
>> ./build.py viewFIFO
>>
>> Thanks!
>> Endre
>>
>> On Sat, Feb 28, 2015 at 6:46 PM, Tristan Gingold <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>     On 28/02/15 00:05, Endre Bak wrote:
>>
>>         Hi,
>>
>>         I ran into an issue which I cannot understand. I suspect it
>>         could be a
>>         bug in GHDL, of course it even can be that I am not aware of a
>> very
>>         trivial coding issue of mine.
>>
>>
>>     Hello,
>>
>>     yes, please send the file so that we can reproduce the issue.
>>
>>     Tristan.
>>
>>
>>         I have two signals:
>>
>>         signal writerClkCntInit: unsigned(1 downto 0) := "00";
>>         signal writerClkCnt: unsigned(1 downto 0) := "00";
>>
>>         At the rising edge of the clock I make an assignment:
>>
>>         report "writerClkCnt <= writerClkCntInit;";
>>         writerClkCnt <= writerClkCntInit;
>>
>>         It is also reflected on the console:
>>
>>         TestFIFO.vhdl:109:24:@1500ns:(__report note): rise
>>         TestFIFO.vhdl:78:32:@1500ns:(__report note): writerClkCnt <=
>>         writerClkCntInit;
>>
>>         In gtkwave, before 1500ns, both signal values are "00". After the
>>         assignment at 1500ns writerClkCnt becomes uninitialized and
>>         writerClkCntInit remains unchanged ("00").
>>
>>         What can cause such anomalies?  May I send the files for analysis?
>>
>>         Thanks,
>>         Endre
>>
>>
>>         _________________________________________________
>>         Ghdl-discuss mailing list
>>         [email protected] <mailto:[email protected]>
>>         https://mail.gna.org/listinfo/__ghdl-discuss
>>         <https://mail.gna.org/listinfo/ghdl-discuss>
>>
>>
>>
>>     _________________________________________________
>>     Ghdl-discuss mailing list
>>     [email protected] <mailto:[email protected]>
>>     https://mail.gna.org/listinfo/__ghdl-discuss
>>     <https://mail.gna.org/listinfo/ghdl-discuss>
>>
>>
>>
>>
>> _______________________________________________
>> Ghdl-discuss mailing list
>> [email protected]
>> https://mail.gna.org/listinfo/ghdl-discuss
>>
>>
>
> _______________________________________________
> Ghdl-discuss mailing list
> [email protected]
> https://mail.gna.org/listinfo/ghdl-discuss
>
_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss

Reply via email to