07:30 <sf-slack2> <arora.prayas> Hi @channel, I changed the vtr source code to fix two build warnings. I want to create a pull request for the same. While adding description for it, I saw that there should be an issue against the changes I propose. Do I file an issue first that can be reproduced to verify my changes ?

07:54 <sf-slack2> <kgugala> Hi @arora.prayas please open an issue where you describe the problem and then create PR where you link to the issue

08:16 <sf-slack2> <arora.prayas> Okay, thanks :)

13:14 <sf-slack2> <arora.prayas> I filed an issue for warnings while building vtr. Here: https://github.com/SymbiFlow/vtr-verilog-to-routing/issues/43

13:14 <tpb> Title: Warnings while bulding VTR · Issue #43 · SymbiFlow/vtr-verilog-to-routing · GitHub (at github.com)

13:25 <sf-slack2> <arora.prayas> I fixed the first two warnings(haven't created a pull request yet). The last warning for possibly dereferencing a null pointer is giving me a hard time. I tried various ways but haven't been able to get around it. One interesting thing to note is that there is no warning message for: _if (child_pbs != nullptr && has_modes())_ but, return child_pbs == nullptr; //or if(child_pbs != nullptr) give a warning:

13:25 <sf-slack2> *warning: potential null pointer dereference [-Wnull-dereference] if (child_pbs != nullptr) ^*

13:29 <sf-slack2> <arora.prayas> I am not trying to fixate on warning issues, neither do I want to waste anybody's time. But generally, any tool should build without any warnings in favour of the user. Often at building time, all warnings are treated as errors.

13:35 <sf-slack2> <arora.prayas> Any help would be appreciated :slightly_smiling_face: