The latest beta release of macOS 11.0 (Big Sur beta 10) seems to have fixed the signed/unsigned confusion. The final release of the OS will be sometime in the next month, so I suggest waiting until then before reverting the workaround patch.
Bryan > On 31/08/2020, at 8:37 PM, Bryan Christianson <br...@whatroute.net> wrote: > > Hi Miroslav > >> On 31/08/2020, at 8:27 PM, Miroslav Lichvar <mlich...@redhat.com> wrote: >> >> Hopefully Apple will fix this soon. It's interesting they had a >> signed/unsigned bug in both adjtime() and ntp_adjtime(). > > I submitted a very simple test case to them - it works correctly in 10.15 and > fails in 11.0. Whether or not they acknowledge it is a bug remains to be > seen, although they were pretty prompt in fixing adjtime() once the error was > reported. > > In the test, I had run time warnings (from asan and friends) with i << 16 - > it didnt like i being a -ve number, so I made the additional tweak of i * (1 > << 16) > > Bryan Christianson > br...@whatroute.net > > > > > -- > To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with > "unsubscribe" in the subject. > For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the > subject. > Trouble? Email listmas...@chrony.tuxfamily.org. > Bryan Christianson br...@whatroute.net -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
