Just took a quick look. See this part of the Makefile and maybe the comment section after this one:
ATOMIC_ACCESS=Pragma-atomic # If using GNAT which supports pragma Atomic for 64-bit scalar variables for GNAT hosted on a 64-bit OS. # You can set this to: # ATOMIC_ACCESS=Pragma-atomic # If the target is 32-bit. "GCC-long-offsets" is a workaround of the GNAT bug on, # that for a 32-bit target pragma Atomic does not support 64-bit scalars even though the processor # has corresponding quad-words instructions. # You need change this to: # ATOMIC_ACCESS=GCC-long-offsets # If using GNAT GPL prior to 2014 or earlier on a 32bit host (Windows or Linux) # You need to change this to: # ATOMIC_ACCESS=GCC-built-ins On Sun, Aug 30, 2020 at 7:22 PM Jeremiah Breeden <jeremiah.bree...@gmail.com> wrote: > It's been a while, but when Gnoga switched from 32bit to 64bit, the > Makefile had a line that had to be manually swapped to enable 32bit. I > don't recall if it was the 32bit or the 64bit option but it had the word > 'atomic' in it. Look towards the beginning of the Makefile. > > On Sun, Aug 23, 2020 at 6:41 PM David Gressett <dgress...@amli-denton.com> > wrote: > >> I'm taking a new look at GNOGA, after giving it some time to develop. I'm >> using the 32-bit TDM-GCC compiler (gcc v9.2.0) on Windows 10. >> >> make BUILD_MODE=Release install fails with 4 attomic access errors: >> >> gnat-sockets-server.ads:1416:22: error: atomic access to "First_Read" >> cannot be guaranteed >> >> The next three errors are very similar; the offenders are "Free_to_Read", >> "First_Written", and "Free_To_Write". >> >> Is there a fix for this? >> >> >> >> _______________________________________________ >> Gnoga-list mailing list >> Gnoga-list@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/gnoga-list >> >
_______________________________________________ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
