public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bachmann dot matt at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/32786] Incorrect code compiles and runs well Date: Tue, 17 Jul 2007 03:39:00 -0000 [thread overview] Message-ID: <20070717033913.6567.qmail@sourceware.org> (raw) In-Reply-To: <bug-32786-14864@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from bachmann dot matt at gmail dot com 2007-07-17 03:39 ------- but thats just it! alright it does not infinite loop but for me it does not crash, it runs perfectly. Here is my output: $ g++ HW1.cpp $ ./a.out 23 Mary had a little lamb. ary had a little lamb. ry had a little lamb. y had a little lamb. had a little lamb. had a little lamb. ad a little lamb. d a little lamb. a little lamb. a little lamb. little lamb. little lamb. ittle lamb. ttle lamb. tle lamb. le lamb. e lamb. lamb. lamb. amb. mb. b. . 15 Thar she blows! har she blows! ar she blows! r she blows! she blows! she blows! he blows! e blows! blows! blows! lows! ows! ws! s! ! Is there any reason that anyone can think of why this would be? I showed my professor and he is the one who suggested I submit a bug. It does this under linux, but in windows using devC++(using a windows port of g++) it breaks as its supposed to. -- bachmann dot matt at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32786
next prev parent reply other threads:[~2007-07-17 3:39 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-17 2:23 [Bug c++/32786] New: " bachmann dot matt at gmail dot com 2007-07-17 3:17 ` [Bug c++/32786] " pinskia at gcc dot gnu dot org 2007-07-17 3:39 ` bachmann dot matt at gmail dot com [this message] 2007-07-17 3:58 ` pinskia at gcc dot gnu dot org 2007-07-17 4:04 ` bachmann dot matt at gmail dot com
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=20070717033913.6567.qmail@sourceware.org \ --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).