-
Notifications
You must be signed in to change notification settings - Fork 767
Remove extra newlines in generated assembly files #19879
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Can you confirm the change in this PR was verified internally with Java 8 build on z/OS or not ?
It was not verified yet. Still working on fully upstreaming all changes across my different branches, I seem to have missed a few files that I am finding out and cleaning up. |
I have launched a Java8 build internally for sanity : http://vmfarm.rtp.raleigh.ibm.com/build_info.php?build_id=75022 Launching sanity build here as well |
jenkins test sanity zlinux jdk21 |
0972fd4
to
62b0a56
Compare
Thanks for the suggestions, I've modified according to feedback and seems to be good with compiling. |
dfc71e8
to
b7db14a
Compare
Please update the commit message: the summary line should not end with a period. |
Similar to previously fixed Open XL errors, there were some more m4 files that generated extra newlines at the end of the generated assembly files. These changes make the tweaks to address this so as to only leave a single newline at the end of these generated assembly files. Signed-off-by: Gaurav Chaudhari <[email protected]>
Jenkins compile zlinux jdk21 |
Similar to previously fixed Open XL errors, there were some more m4 files that generated extra newlines at the end of the generated assembly files. These changes make the tweaks to address this so as to only leave a single newline at the end of these generated assembly files.