| *** tpb has joined #vtr-dev | 00:00 | |
| *** vtrbot has quit IRC | 04:34 | |
| *** vtrbot has joined #vtr-dev | 05:01 | |
| mithro | kem_: There is an example of what the clang-format run output would look like at https://github.com/kgugala/vtr-verilog-to-routing/commit/bae35143d8728674b6941f3b11cfd23a469508c1#diff-ab03a6d043b974937b0bc52ea8b94eb9 | 17:57 |
|---|---|---|
| tpb | Title: run code-format · kgugala/vtr-verilog-to-routing@bae3514 · GitHub (at github.com) | 17:57 |
| litghost | kem_: Please re-open https://github.com/verilog-to-routing/vtr-verilog-to-routing/issues/485, as the issue does not go away even with more reasonable timing values | 19:06 |
| tpb | Title: Issues · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com) | 19:06 |
| litghost | kem_: In fact the routing graph generated by VPR also replicates the issue | 19:06 |
| litghost | kem_: And the timing input is basically from the VPR example arch | 19:07 |
| kem_ | litghost: Fixing the timing values on the test case fixed the issue for me. But if there are examples with realistic delays which cause the same issue I can definitely re-open it. | 20:30 |
| litghost | kem_: Already attached a new graph | 20:31 |
| kem_ | mithro: The formatting looks pretty good | 21:44 |
| kem_ | mithro: There are a just couple things that look a little odd, such as inserting an extra space before c++-style comments and a couple places where multi-line conditions are a bit off | 21:46 |
| mithro | kem_: example? | 21:46 |
| kem_ | mithro: can't figure out how to link to specific lines from that commit... | 21:48 |
| mithro | kem_: Just click on the line numbers and then copy the url? | 21:48 |
| kem_ | mithro: doesn't seem to change the url | 21:49 |
| mithro | kem_: You looking at https://github.com/kgugala/vtr-verilog-to-routing/commit/bae35143d8728674b6941f3b11cfd23a469508c1#diff-cb6d86211fc138d5f2a87ba2ac745365L139 ? | 21:49 |
| tpb | Title: run code-format · kgugala/vtr-verilog-to-routing@bae3514 · GitHub (at github.com) | 21:49 |
| kem_ | mithro: OK I missed the line number at the end of the commit id :) | 21:50 |
| kem_ | mithro: Extra space before c++ comment https://github.com/kgugala/vtr-verilog-to-routing/commit/bae35143d8728674b6941f3b11cfd23a469508c1#diff-6f0adcb7b2f19840e79075d70401da42L91 | 21:51 |
| tpb | Title: run code-format · kgugala/vtr-verilog-to-routing@bae3514 · GitHub (at github.com) | 21:51 |
| mithro | kem_: Ahh, I see | 21:51 |
| kem_ | mithro: I'm not set on this one, but I still miss the indent around public/private (https://github.com/kgugala/vtr-verilog-to-routing/commit/bae35143d8728674b6941f3b11cfd23a469508c1#diff-1819e1ce829cfffbd9a42da54338b406L82) | 21:54 |
| tpb | Title: run code-format · kgugala/vtr-verilog-to-routing@bae3514 · GitHub (at github.com) | 21:54 |
| kem_ | mithro: For single line if bodies I prefer them on the same line as the if or with braces (in the future avoids accidentally adding something that is indented to appear as part of the body but actually is not). For example: https://github.com/kgugala/vtr-verilog-to-routing/commit/bae35143d8728674b6941f3b11cfd23a469508c1#diff-31ec6c191fb261c72ad6804a23bf1a26L504 | 21:56 |
| tpb | Title: run code-format · kgugala/vtr-verilog-to-routing@bae3514 · GitHub (at github.com) | 21:56 |
| kem_ | mithro: Also some funny formatting with these multi-line expressions (https://github.com/kgugala/vtr-verilog-to-routing/commit/bae35143d8728674b6941f3b11cfd23a469508c1#diff-db8d7b991af7b9051a745c120f1ef2b0R510). I generally try to line up the operators at the left so it's easier to read. | 22:05 |
| tpb | Title: run code-format · kgugala/vtr-verilog-to-routing@bae3514 · GitHub (at github.com) | 22:05 |
| mithro | kem_: https://github.com/mithro/vtr-verilog-to-routing/commit/c353d7b4f8375c554b3b27efec56ee6e49f9206e | 22:08 |
| tpb | Title: run code-format · mithro/vtr-verilog-to-routing@c353d7b · GitHub (at github.com) | 22:08 |
| mithro | kem_: That uses an offset of -2 for the member private/public/protected labels | 22:08 |
| mithro | kem_: Was there a decision about how long lines should be? | 22:31 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!