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.
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
Implement GNU Make 4.4+ jobserver fifo / semaphore client support #2450
base: master
Are you sure you want to change the base?
Implement GNU Make 4.4+ jobserver fifo / semaphore client support #2450
Changes from all commits
f57dd71
8223097
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I suggest not changing this method's signature at all, to minimize changes.
Since the flag value is not going to change during a build, you can simply pass
plan_.JobserverEnabled()
to theRealCommandRunner
constructor to record its value, and haveRealCommandRunner::CanRunMore()
returnSIZE_MAX
when the flag is enabled.This should work identically, without having to change the DryCommandRunner and TestCommandRunner interfaces / implementations.
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.
Good point.
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.
from the Make manual:
I have not looked at Make's code relevant to this yet, so I don't know the significance. It might be that the character being anything other than a
+
is a rare occurence... maybe someone else can clarify how important it is.I will follow up with another comment with more information as I continue to play with the PR's changes and review Make's source.
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.
Yeah, I've noticed the same from the Make manual. It might make sense to store the acquired token in the (recently added)
Edge::acquired_job_server_token_
member. I'll look into it.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.
After looking at GNU Make source history, I changed my mind. I don't think this is important. There is no sign that they are going to introduce new characters that have special meaning, and if they somehow do that, it would be pretty easy to add support for it later. Let's save the idea for the future...