PR #2553 already inserted a flip-flop to filter source glitches if the target was asynchronous, but this is incomplete. The problem exists for both asynchronous and synchronous target domains. Any source glitches can actually unintendedly end up in the dual flip-flop synchronizer of a synchronous target as well.
Still TODO:
[x] Write a changelog entry (see changelog/README.md)
[x] Check copyright notices are up to date in edited files
PR #2553 already inserted a flip-flop to filter source glitches if the target was asynchronous, but this is incomplete. The problem exists for both asynchronous and synchronous target domains. Any source glitches can actually unintendedly end up in the dual flip-flop synchronizer of a synchronous target as well.
Still TODO: