-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Stty: Implemented input and output baud rate setting for stty #9517
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
GNU testsuite comparison: |
5097f92 to
a1c0044
Compare
|
GNU testsuite comparison: |
a1c0044 to
5a54163
Compare
|
GNU testsuite comparison: |
|
Hmm an issue with one of the baud rate integration tests came up, was covered up by the seq failure before |
5a54163 to
2903ff7
Compare
|
Darn so it used to be back before 9.2 that it would except invalid arguments without failing? |
|
GNU testsuite comparison: |
CodSpeed Performance ReportMerging #9517 will not alter performanceComparing Summary
Footnotes
|
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
on different platforms the output is different due to different versions so cannot use this as a test.
1f6ede8 to
d018ba7
Compare
|
GNU testsuite comparison: |
There's two other open stty PR's: #9490 and #9516 . Once those two are merged all of the stty tests pass except for the bad-speed test. This test overrides cfsetispeed and checks to see if it is called. Currently our implementation of stty only overrides the cfsetospeed. The support to do both in GNU existed for a while. I changed the enum and parser to treat the ispeed and ospeed seperately and I added integration tests that compare that using those new flags matches the input and output of the GNU implementation.