public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paulo_torrens at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/56180] Strange behaviour with optimization (using K&R C) Date: Sat, 02 Feb 2013 21:45:00 -0000 [thread overview] Message-ID: <bug-56180-4-dx8sfp4Lkl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56180-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56180 --- Comment #3 from Paulo Torrens <paulo_torrens at hotmail dot com> 2013-02-02 21:45:20 UTC --- According to the man page here on Mac: Only one character of push-back is guaranteed, but as long as there is sufficient memory, an effectively infinite amount of push-back is allowed. And yeah, you are right (thank you!), that j was one byte ahead, but, still... shouldn't the behaviour be the same across optimization levels?
next prev parent reply other threads:[~2013-02-02 21:45 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-02 9:00 [Bug c/56180] New: " paulo_torrens at hotmail dot com 2013-02-02 10:49 ` [Bug c/56180] " jakub at gcc dot gnu.org 2013-02-02 11:15 ` jakub at gcc dot gnu.org 2013-02-02 21:45 ` paulo_torrens at hotmail dot com [this message] 2013-02-03 9:22 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-56180-4-dx8sfp4Lkl@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).