From: david.brown@hesbynett.no   
      
   On 26/11/2025 11:01, Michael S wrote:   
   > On Tue, 25 Nov 2025 13:42:37 -0800   
   > Keith Thompson  wrote:   
   >   
   >> David Brown  writes:   
   >> [...]   
   >>> But the _BitInt version is definitely neater.  I can see myself   
   >>> using _BitInt(12) and similar sizes for things like values read from   
   >>> hardware sensors of different resolutions.   
   >>>   
   >>> (The code for all three is the same with gcc on x86 or arm64 -   
   >>> unfortunately, gcc does not yet support _BitInt on many targets.)   
   >> [...]   
   >>   
   >> Is support for _BitInt limited by target or by version?   
   >>   
   >> It looks like _BitInt support was introduced in gcc 14.1.0.  You might   
   >> have older versions of gcc on other platforms.   
   >>   
   >   
   > The most recent version of arm-none-eabi-gcc in my distribution of   
   > choice (msys2) is 13.3.0.   
   > I am too lazy to compile arm-none-eabi-gcc from source. Would rather   
   > wait.   
   > I suppose, David is like me in that regard, except that he probably   
   > uses even more conservative distribution.   
   >   
   >   
      
   I have release 13.3 installed, but I haven't used it on any projects   
   yet.  I tend to use new releases on new projects, but I am very   
   conservative about changing toolchains in existing projects.   
      
   But for things like this, I use godbolt.org - it is /so/ much easier   
   than testing individually.  Just pick the compiler target and version   
   from the list, and see if you get an error message when using _BitInt.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)