configure: Rerun bootstrap on modern platform.

[InterLinked1]

The last time configure was run, it was run on a system that
did not enable -std=gnu11 by default, which meant that the
restrict qualifier would not be recognized on certain platforms.
This regenerates the configure files from running bootstrap.sh,
so that these should be recognized on all supported platforms.

Resolves: #586

[github-actions]

REMINDER: If this PR applies to other branches, please add a comment with the appropriate "cherry-pick-to" headers as per the Create a Pull Request process.

If you don't want it cherry-picked, please add a comment with cherry-pick-to: none so we don't keep asking.

If, after adding "cherry-pick-to" comments, you change your mind, please edit the comment to DELETE the header lines and add cherry-pick-to: none.

The currently active branches are now 18, 20, 21 and master.

[seanbright]

Out of curiosity, what does using restrict here buy you? There don't appear to be any optimization opportunities here for the compiler so I am wondering what the upside is?

[InterLinked1]

Out of curiosity, what does using restrict here buy you? There don't appear to be any optimization opportunities here for the compiler so I am wondering what the upside is?

It's not a huge deal in this particular case, but we should be able to use restrict in general if needed, so I'm just doing this now rather than punting it.

[seanbright]

I guess what I really meant to ask was - what is the benefit of using restrict in this specific case?

[InterLinked1]

I guess what I really meant to ask was - what is the benefit of using restrict in this specific case?

Not that much, I suppose. You're right there's no performance benefit since it's not also reading. It's mostly semantic in that that variable isn't being used anywhere else. Do you think it should be removed?

[seanbright]

I don't have an opinion, I was just trying to understand the rationale for it being there in the first place.

[InterLinked1]

cherry-pick-to: none

[seanbright]

The title and description of this PR is now in conflict with what is actually being proposed.

[InterLinked1]

The title and description of this PR is now in conflict with what is actually being proposed.

The commit message is correct.

The PR doesn't update automatically, but I'll sync it now.

[seanbright]

I know that the commit message is correct. I mentioned the title and description of the PR. Thank you for making the change.

[gtjoseph]

Tested on CentOS 7 with gcc (GCC) 4.8.5 20150623 and ./configure now correctly sets CC=gcc -std=gnu11 in makeopts.

[gtjoseph]

The cherry-picks all failed so I think you're gonna have to submit a PR for each branch :(

[github-actions]

Successfully merged to branch master.