Thanks to visit codestin.com
Credit goes to github.com

Skip to content

configure: Rerun bootstrap on modern platform.#587

Merged
asterisk-org-access-app[bot] merged 1 commit into
asterisk:masterfrom
InterLinked1:master-issue-586
Feb 12, 2024
Merged

configure: Rerun bootstrap on modern platform.#587
asterisk-org-access-app[bot] merged 1 commit into
asterisk:masterfrom
InterLinked1:master-issue-586

Conversation

@InterLinked1

@InterLinked1 InterLinked1 commented Feb 8, 2024

Copy link
Copy Markdown
Contributor

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

github-actions Bot commented Feb 8, 2024

Copy link
Copy Markdown

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

Copy link
Copy Markdown
Contributor

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

Copy link
Copy Markdown
Contributor Author

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

Copy link
Copy Markdown
Contributor

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

@InterLinked1

Copy link
Copy Markdown
Contributor Author

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

Copy link
Copy Markdown
Contributor

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

Comment thread configure.ac Outdated
Comment thread channels/chan_iax2.c Outdated
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: asterisk#586
@InterLinked1

InterLinked1 commented Feb 9, 2024

Copy link
Copy Markdown
Contributor Author

cherry-pick-to: none

@seanbright

Copy link
Copy Markdown
Contributor

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

@InterLinked1

Copy link
Copy Markdown
Contributor Author

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.

@InterLinked1 InterLinked1 changed the title chan_iax2: Only use restrict qualifier if supported. configure: Rerun bootstrap on modern platform. Feb 10, 2024
@seanbright

Copy link
Copy Markdown
Contributor

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

@gtjoseph

Copy link
Copy Markdown
Member

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

@gtjoseph gtjoseph added the cherry-pick-test Trigger dry run of cherry-picks label Feb 12, 2024
@github-actions github-actions Bot added cherry-pick-testing-in-progress Cherry-Pick tests in progress cherry-pick-checks-failed Cherry-Pick checks failed and removed cherry-pick-test Trigger dry run of cherry-picks cherry-pick-testing-in-progress Cherry-Pick tests in progress labels Feb 12, 2024

@gtjoseph gtjoseph left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@github-actions

Copy link
Copy Markdown

Successfully merged to branch master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[bug]: The "restrict" keyword used in chan_iax2.c isn't supported in older gcc versions

3 participants