Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Update sljit to current master#791

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
NWilson merged 1 commit intomasterfromuser/niwilson/sljit-update
Sep 12, 2025
Merged

Conversation

@NWilson
Copy link
Member

This is a routine update, so that we can enforce the-Wimplicit-fallthrough warning to our CI afterzherczeg/sljit#330.

@NWilson
Copy link
MemberAuthor

Unfortunately the build fails. Attempt at fix over here:zherczeg/sljit#331

@zherczeg
Copy link
Collaborator

@carenas it looks like there is still more combinations... :(

@carenas
Copy link
Contributor

@carenas it looks like there is still more combinations... :(

fixing-Wundef should be straight forward; relying too much in__has*attribute() might not be worth doing though, as we know clang has a broken implementation of__has_attribute(fallthrough) in older versions.

@NWilsonNWilsonforce-pushed theuser/niwilson/sljit-update branch from1d67ec6 tod604879CompareSeptember 12, 2025 12:18
@NWilsonNWilson merged commit0686e42 intomasterSep 12, 2025
35 checks passed
@NWilsonNWilson deleted the user/niwilson/sljit-update branchSeptember 12, 2025 13:12
@zherczeg
Copy link
Collaborator

Note: a feature development is in progress, so the current sljit does not compile everywhere. Another update will be needed.

@NWilson
Copy link
MemberAuthor

Thanks! I'm happy for PCRE2 master to track sljit master, and for them both to be work-in-progress.

We could even do a regular (automated?) weekly merge. Or just manual - I don't mind.

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@NWilson@zherczeg@carenas
[8]ページ先頭
©2009-2025 Movatter.jp