Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-91150

Address Android's Top-byte Ignore feature

    XMLWordPrintable

Details

    • Android
    • 2021wk50POAndroid&Mobile, 2022wk02FOAndroid&Automotive, 2022wk04FOAndroid&Automotive, 2022wk06FOAndroid&Automotive
    • c7722d4ed (dev), 73f1fa8a8 (6.5), b0907db9e (dev), 6979f718b (6.5), 028a31b50 (dev), 1cf9392ad (6.6), e2b415bd2 (tqtc/lts-6.5)

    Description

      On recent versions of Android, top-byte ignore is enabled if the target SDK is high enough (https://source.android.com/devices/tech/debug/tagged-pointers).
      This breaks QML's NaN-tagging scheme.

      Attachments

        Issue Links

          is required for

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-97009 Broken rendering on Qt 6.2 Android arm64-v8a

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. QTBUG-99164 Android 11 features

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Open

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. QTBUG-98438 Android 11 support

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-97009 Broken rendering on Qt 6.2 Android arm64-v8a

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-101080 QT 5.15.2 and recent mobile devices running Android 11 (API 30) = FAILURE

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-111780 QJSValue misbehaves on android

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-56264 Creating a QJSEngine results in a segfault on Sparc64

          • P3: Somewhat important - Should be fixed, but doesn't affect the release in any way.
          • Closed
          resulted in

          Task - A task that needs to be done. QTBUG-101686 QV4::Value: Research different tagging scheme

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              ulherman Ulf Hermann
              fabiankosmale Fabian Kosmale
              Votes:
              5 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: