TFW someone reports a "Yosys bug" and it turns out it is a 100 MHz design and they did not even bother running timing analysis.
-
-
Replying to @oe1cxw
.. I even had someone once report a "bug" in a >> 100 MHz design and they ran timing and it said 25 MHz is OK and they just ignored that.
1 reply 0 retweets 6 likes -
Replying to @oe1cxw
A common pattern here: Those are the bug reports that come with a vague description and a bogus argument why they can't share their code.
1 reply 0 retweets 9 likes -
Replying to @oe1cxw
can you just make it policy that every bug report must come with Verilog that reproduces it?
1 reply 0 retweets 1 like -
Replying to @whitequark
This *IS* the policy. They argue with me that their case is special.. of course.
1 reply 0 retweets 2 likes -
Replying to @oe1cxw
i guess that's what the "lock conversation" button there is for
1 reply 0 retweets 5 likes -
Replying to @whitequark
Oh, yes! Usually they send me emails, don't use the recommended public channels. Most people who waste my time prefer to do that in private.
1 reply 0 retweets 5 likes -
-
Replying to @whitequark
Here is an example that actually started on github: https://github.com/cliffordwolf/icestorm/issues/36 … he later sent emails to me and people I work with.
1 reply 0 retweets 1 like
He sent various code snippets but never a complete example and continuously complained to people I work with that I am unfairly ignoring him
-
-
Replying to @oe1cxw @whitequark
Months later I got a complete example: Turns out he was trying to generate a 250 MHz LVDS signal and he ignored timing analysis results.
1 reply 0 retweets 5 likes -
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.