Skip to content
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

module: unicode: #if out unused bits of libunicode (#13224) #16704

Closed

Conversation

nabijaczleweli
Copy link
Contributor

@nabijaczleweli nabijaczleweli commented Oct 30, 2024

Motivation and Context

The second (non-uconv) half of #13224, minus U8_TEXTPREP_NOWAIT, U8_VALIDATE_CHECK_ADDITIONAL, and U8_VALIDATE_UCS2_RANGE (rejected in review below)

Description

The API remains, the removed bits are #ifed out.

$ size -G ./module/zfs.ko ./module/zfs.new.ko
      text       data        bss      total filename
   2865126    1597982     755768    5218876 ./module/zfs.ko
   2864038    1429784     755768    5049590 ./module/zfs.new.ko
     -1088    -168198
       -1k      -164k

How Has This Been Tested?

Builds.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Performance enhancement (non-breaking change which improves efficiency)
  • Code cleanup (non-breaking change which makes code smaller or more readable)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
  • Documentation (a change to man pages or other documentation)

Checklist:

  • My code follows the OpenZFS code style requirements.
  • I have updated the documentation accordingly.
  • I have read the contributing document.
  • I have added tests to cover my changes. — none apply
  • I have run the ZFS Test Suite with this change applied. — CI take my hand
  • All commit messages are properly formatted and contain Signed-off-by.

Copy link
Member

@amotin amotin left a comment

Choose a reason for hiding this comment

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

Looks better to me, but lets fix style, build and one more comment:

@nabijaczleweli nabijaczleweli force-pushed the utf8-hehe-libunicode branch 2 times, most recently from 0e4df33 to 6ff1bb0 Compare October 30, 2024 17:16
@amotin amotin added the Status: Code Review Needed Ready for review and testing label Oct 30, 2024
Copy link
Member

@amotin amotin left a comment

Choose a reason for hiding this comment

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

Have no objections, assuming it will pass the tests. Thanks.

@amotin
Copy link
Member

amotin commented Nov 1, 2024

  module/unicode/u8_textprep.c: In function 'do_case_conv':
  module/unicode/u8_textprep.c:555:12: error: 'i' may be used uninitialized [-Werror=maybe-uninitialized]
    555 |         u8s[i] = '\0';
        |            ^
  module/unicode/u8_textprep.c:463:16: note: 'i' was declared here
    463 |         size_t i;
        |                ^

@nabijaczleweli
Copy link
Contributor Author

I don't get this warning but fixed hopefully

@amotin
Copy link
Member

amotin commented Nov 1, 2024

I don't know why checkstyle does not complain, but one of your commit messages has too long title. Please reformat. I am also not sure this worth 3 individual commits.

With the previous patch this yields
  $ size -G ./module/zfs.ko ./module/zfs.new.ko
        text       data        bss      total filename
     2865126    1597982     755768    5218876 ./module/zfs.ko
     2864038    1429784     755768    5049590 ./module/zfs.new.ko
       -1088    -168198
         -1k      -164k

Signed-off-by: Ahelenia Ziemiańska <[email protected]>
@behlendorf behlendorf added Status: Accepted Ready to integrate (reviewed, tested) and removed Status: Code Review Needed Ready for review and testing labels Nov 5, 2024
@behlendorf behlendorf closed this in 5e72677 Nov 5, 2024
behlendorf pushed a commit that referenced this pull request Nov 5, 2024
Reviewed-by: Brian Behlendorf <[email protected]>
Reviewed-by: Alexander Motin <[email protected]>
Signed-off-by: Ahelenia Ziemiańska <[email protected]>
Closes #16704
behlendorf pushed a commit that referenced this pull request Nov 5, 2024
With the previous patch this yields
  $ size -G ./module/zfs.ko ./module/zfs.new.ko
        text       data        bss      total filename
     2865126    1597982     755768    5218876 ./module/zfs.ko
     2864038    1429784     755768    5049590 ./module/zfs.new.ko
       -1088    -168198
         -1k      -164k

Reviewed-by: Brian Behlendorf <[email protected]>
Reviewed-by: Alexander Motin <[email protected]>
Signed-off-by: Ahelenia Ziemiańska <[email protected]>
Closes #16704
lundman pushed a commit to openzfsonwindows/openzfs that referenced this pull request Jan 26, 2025
Reviewed-by: Brian Behlendorf <[email protected]>
Reviewed-by: Alexander Motin <[email protected]>
Signed-off-by: Ahelenia Ziemiańska <[email protected]>
Closes openzfs#16704
lundman pushed a commit to openzfsonwindows/openzfs that referenced this pull request Jan 26, 2025
Reviewed-by: Brian Behlendorf <[email protected]>
Reviewed-by: Alexander Motin <[email protected]>
Signed-off-by: Ahelenia Ziemiańska <[email protected]>
Closes openzfs#16704
lundman pushed a commit to openzfsonwindows/openzfs that referenced this pull request Jan 26, 2025
With the previous patch this yields
  $ size -G ./module/zfs.ko ./module/zfs.new.ko
        text       data        bss      total filename
     2865126    1597982     755768    5218876 ./module/zfs.ko
     2864038    1429784     755768    5049590 ./module/zfs.new.ko
       -1088    -168198
         -1k      -164k

Reviewed-by: Brian Behlendorf <[email protected]>
Reviewed-by: Alexander Motin <[email protected]>
Signed-off-by: Ahelenia Ziemiańska <[email protected]>
Closes openzfs#16704
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Accepted Ready to integrate (reviewed, tested)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants