Bug 1956103

Summary: Verilator package nonfunctional with F34's GCC 11.
Product: [Fedora] Fedora Reporter: Jake Merdich <jake>
Component: verilatorAssignee: Scott Tsai <scottt.tw>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: marcus, scottt.tw
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-08 00:51:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Output on a fresh F34 machine none

Description Jake Merdich 2021-05-02 18:49:49 UTC
Description of problem:
'Verilated' code does not compile with GCC 11 (default compiler on F34+). 'Verilator' generates c++ code from Verilog code, which is subsequently compiled with GCC/G++. This generated code is missing an `#include <limits>` which means that verilator is mostly nonfunctional on F34 and Rawhide. 

**This was fixed upstream with https://github.com/verilator/verilator/pull/2747, which is probably trivial enough to cherry pick.**

Version-Release number of selected component (if applicable):
verilator-4.108-2.fc34.x86_64 (any 4.108.x works)
gcc-c++-11.1.1-1.fc34.x86_64 (any 11.x works)

How reproducible: 100%


Steps to Reproduce:
1. Install g++ and verilator
2. Create a trivial verilog file 'out.v' (content doesn't really matter, taken from example on verilator docs):

  module our;
     initial begin $display("Hello World"); $finish; end
  endmodule

3. 'Verilate' and compile the file with 'verilator --cc --exe --build our.v'

Actual results:
  Build fails with missing 'std::numeric_limits' (see attached log)

Expected results:
  Build passes and an exe is generated


Additional info:

Comment 1 Jake Merdich 2021-05-02 18:50:53 UTC
Created attachment 1778665 [details]
Output on a fresh F34 machine

Comment 2 Ben Cotton 2022-05-12 16:32:59 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ben Cotton 2022-06-08 00:51:48 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.