Remove leading / trailing '\\' in SDC signal names (copy #2129) - #2142
Merged
Conversation
* Remove leading / trailing '\\' in SDC signal names
In SDC files, escaped identifiers should not be rendered with
leading trailing backslashes as this causes faults in vendor tools
like Quartus.
* Generate basic identifiers for port names
When generating port names, Clash now always generates basic identifiers
instead of extended identifiers. This means when choosing a name for a
hidden control line, it will now generate something like
d_0
where before it would have generated something like
d(%,,%)_0
These extended identifiers can cause problems with some tooling, as
less permissive tooling will complain about the use of special TCL
characters, or the presence / lack of escaping for the identifier.
(cherry picked from commit a0c4f19)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is an automatic copy of pull request #2129 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com