On 07/12/2018 08:42 AM, Mahmood Naderan via gcc-help wrote: > Still I wonder why that is called undefined behavior?! Don't guess. If you're debugging at this level, you must look at the code. Use disp/i $pc, and then step through, one instruction at a time. It's the only way to learn. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. <https://www.redhat.com> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
