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

Cannot build with clang & ubsan on AArch64 Linux

    XMLWordPrintable

Details

    • Linux/Wayland, Linux/X11

    Description

      Hello,

      Platform: AArch64 Linux with Clang as a compiler. On this particular example I'm on Fedora 41 (Asahi Linux).

      Due to this long-standing LLVM issue – https://github.com/llvm/llvm-project/issues/16778 ; https://reviews.llvm.org/D141836  – it is not possible to use int128 on many AArch64 platforms when using ubsan, as this generates calls to symbols not implemented by the platform's libgcc (which may be desireable to use when linking against system libraries), such as __muloti4 

      Sadly, trying to disable int128 support with  -DQT_NO_INT128 now yields, since qtbase@feb43b779ac 

      qtbase/src/corelib/global/qtypes.cpp:508:4: error: Qt needs to be compiled in a mode that enables INT128     if the compiler supports it in principle. 
 508 | #  error Qt needs to be compiled in a mode that enables INT128 \ 
     |    ^

      Thus this is between a rock and a hard place with no proper way to build.

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. QTQAINFRA-6203 missing gcc 12/13/14 in CI

          • 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
          resulted from

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-119901 Basic <type_traits> not working for q*int128 in QtCore TUs

          • 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
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              cnn Qt Core & Network
              jcelerier Jean-Michaël Celerier
              Vladimir Minenko Vladimir Minenko
              Alex Blasche Alex Blasche
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes