From: david.brown@hesbynett.no   
      
   On 23/11/2025 01:14, bart wrote:   
   > On 22/11/2025 23:24, Keith Thompson wrote:   
   >> bart  writes:   
   >>> On 22/11/2025 17:35, bart wrote:   
   >>>> On 22/11/2025 17:13, Bonita Montero wrote:   
   >>>>> You can compile the code with -mavx512bw.   
   >>>>> This is "inline.h":   
   >>>> But I now get, from:   
   >>>>     g++ =std=c++23 -mavx512bw -O2 c.cpp   
   >>>> the errors shown below. I tried -fconcepts too.   
   >>>> So, what also do I need? (So far you're not selling C++ very well!)   
   >>>   
   >>> Wait, there's a "=std" in that command line instead of   
   >>> "-std". Apparently it is not an error (?).   
   >> [...]   
   >>   
   >> It seems that gcc and g++ interpret any unrecognized command line   
   >> argument as the name of a "linker input file".   
   >   
   > It looks like it compiles any source code first, so won't get around to   
   > reporting an error if that compilation fails.   
      
   Correct.  Compile first, then link - that has to be the order of   
   business.  So if the compilation fails, gcc or g++ (which are just   
   "driver" programs that start the real compiler, assembler, and linker)   
   doesn't get a far as trying to link, and thus doesn't get as far as   
   looking to see if this mysterious "=std=c++23" file exists or not.   
      
   gcc will happily complain when you give it an incorrect or unknown   
   option, but it has to recognise that it /is/ an option!   
      
   >   
   >> BTW, comp.lang.c++ is down the hall, just past the water cooler.   
   >   
   >   
   > This was supposed be about comparing a C approach to C++. Except there   
   > were problems in getting the 'fast' C++ code to compile and then to run.   
   >   
   > I think I'll stick with the simple C version which can also be trivially   
   > ported to any language as there are no heavy dependencies.   
   >   
      
   Bonita has a years-long habit of interrupting C discussions with C++   
   distractions.  I agree that sometimes a comparison to different   
   languages is relevant in a C discussion, but for C++ details it is   
   better to move over to c.l.c++.   
      
   However, this code is neither C nor C++ - it is x86 assembly, wrapped in   
   some C++ and a whole lot of Bonita-specific stuff.  I've no idea if   
   there is a suitable forum for that!   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)