Stucki wrote:
> > When I change "set nrformats-=octal" in defaults.vim to something that > > is not 8 bytes, then the report goes away. > > If I set another buffer-local variable to a value with 8 bytes that > > one is also reported. I don't think Vim itself does something special > > for an 8 byte string. > > Strange ... BUT, could you try to run the test with binaries > compiled with different 'compiler optimisation levels'. We once > had an error, which went away, if we lowered/raised the level > form our default=2 only on 2 it happened, and then we noticed > it happened only on a specific kind of CPU. Something in the > combination of possible registers on the CPU and the way the > parameters of routines were handled by optimizing, lost one > word of memory and potentially crashed the program. Crashes > happened on a small subset of our desktop PCs. I tried with -g (no optimization) -O1, -O2 and got the same results. My CPU is a Ryzen 2700X -- "Hegel was right when he said that we learn from history that man can never learn anything from history." (George Bernard Shaw) /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/201909301836.x8UIaj0K018721%40masaka.moolenaar.net.
