Fix strchr() and related functions for ISO C23 compliance#3570
Open
purofle wants to merge 78 commits intowarmcat:mainfrom
Open
Fix strchr() and related functions for ISO C23 compliance#3570purofle wants to merge 78 commits intowarmcat:mainfrom
purofle wants to merge 78 commits intowarmcat:mainfrom
Conversation
Since glibc-2.43: For ISO C23, the functions bsearch, memchr, strchr, strpbrk, strrchr, strstr, wcschr, wcspbrk, wcsrchr, wcsstr and wmemchr that return pointers into their input arrays now have definitions as macros that return a pointer to a const-qualified type when the input argument is a pointer to a const-qualified type. Signed-off-by: purofle <yuguo.or@isrc.iscas.ac.cn>
Includes ${EXTIP4} and ${EXTIP6} for signing server's external IPs.
${DANE0} and ${DANE1} interpret the dane definition that's ongoing and look
for the matching tls certificate to produce the hash
These are from 16 old Coverity hits that I dismissed in my Coverity UI... of course any other coverity user testing it doesn't get to know my assessment. So these are an attempt to silence these false positives by either commenting the code as OK for Coverity to read, or modifying it to avoid whatever it thought was happening the other way.
This simpifies enabling build of the -camshow example by LWS_WITH_WEBRTC
Normally mounts are happening at URL "directories"... this new extact_match
("exact-match" for lejp-conf) bool allows you to force the whole mountpoint
path to match, so you can apply a mount at a specific path including the
filename when you need to.
lws-team
force-pushed
the
main
branch
6 times, most recently
from
9703105 to
b1c5c37
Compare
lws-team
force-pushed
the
main
branch
11 times, most recently
from
81c372a to
4a63b93
Compare
lws-team
force-pushed
the
main
branch
5 times, most recently
from
89537f6 to
9d37567
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Since glibc-2.43:
For ISO C23, the functions bsearch, memchr, strchr, strpbrk, strrchr, strstr, wcschr, wcspbrk, wcsrchr, wcsstr and wmemchr that return pointers into their input arrays now have definitions as macros that return a pointer to a const-qualified type when the input argument is a pointer to a const-qualified type.
The compilation test passed on my Glibc 2.43 system.