From: "James Gregory" <james.jrg@gmail.com>
To: "Chris Jefferson" <chris@bubblescope.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Including <iostream> affects whether or not program freezes?
Date: Sat, 12 Jul 2008 22:11:00 -0000 [thread overview]
Message-ID: <beb51c260807121446t5f3328dds7b9f9d4e3a712bf7@mail.gmail.com> (raw)
In-Reply-To: <beb51c260807121338p6fc40a1dga8adbf5f68a82fc3@mail.gmail.com>
On Sat, Jul 12, 2008 at 9:38 PM, James Gregory <james.jrg@gmail.com> wrote:
In a more readable fashion, the difference between the two versions is:
///////////////
Include <iostream>, no freeze:
///////////////
;; Function bool AIInterpreter::is_group_like_this(int, int, bool,
bool) (_ZN13AIInterpreter18is_group_like_thisEiibb)
Removing basic block 39
bool AIInterpreter::is_group_like_this(int, int, bool, bool) (this,
n_side, n_group, discount_dead, discount_our)
{
unsigned char temp.4650;
unsigned char temp.4649;
unsigned char temp.4648;
const unsigned char * D.86270;
unsigned char D.86219;
const unsigned char * D.86202;
unsigned char D.86165;
const unsigned char * D.86148;
<L39>:;
D.86165 = *D.86148;
if (D.86165 == 157) goto <L36>; else goto <L40>;
<L40>:;
if (D.86165 == 158) goto <L36>; else goto <L166>;
<L166>:;
D.86148 = this->l_iter._M_current + 1B;
this->l_iter._M_current = D.86148;
if (this->l_end._M_current == D.86148) goto <L36>; else goto <L39>;
///////////////
Don't include <iostream>, freeze:
///////////////
;; Function bool AIInterpreter::is_group_like_this(int, int, bool,
bool) (_ZN13AIInterpreter18is_group_like_thisEiibb)
Removing basic block 39
bool AIInterpreter::is_group_like_this(int, int, bool, bool) (this,
n_side, n_group, discount_dead, discount_our)
{
const unsigned char * this___l_iterthis__I___M_currentthis____.4618;
const unsigned char * this___l_iterthis__I___M_currentthis____.4617;
const unsigned char * this___l_iterthis__I___M_currentthis____.4616;
unsigned char D.86198;
unsigned char D.86144;
<L120>:;
this___l_iterthis__I___M_currentthis____.4616 = (const unsigned char
*) ((long unsigned int) D.86143 + 1);
Invalid sum of incoming frequencies 873, should be 0
<L40>:;
this___l_iterthis__I___M_currentthis____.4616 = (const unsigned char
*) ((long unsigned int) this___l_iterthis__I___M_currentthis____.4616
+ 1);
if (D.86144 == 157) goto <L162>; else goto <L40>;
Invalid sum of incoming frequencies 0, should be 301
<L162>:;
this->l_iter._M_current = this___l_iterthis__I___M_currentthis____.4616;
D.68741 = 0;
goto <bb 42> (<L174>);
prev parent reply other threads:[~2008-07-12 21:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 3:26 James Gregory
2008-07-09 12:03 ` Lionel B
2008-07-09 16:49 ` James Gregory
2008-07-09 18:08 ` Burlen Loring
2008-07-09 13:43 ` Andrew Bell
2008-07-09 14:35 ` Andrew Haley
2008-07-09 17:02 ` Chris Jefferson
2008-07-10 10:58 ` James Gregory
2008-08-05 6:45 ` Christoph Bartoschek
2008-08-05 9:31 ` James Gregory
2008-07-12 21:16 ` James Gregory
2008-07-12 21:05 ` James Gregory
2008-07-12 22:11 ` James Gregory [this message]
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=beb51c260807121446t5f3328dds7b9f9d4e3a712bf7@mail.gmail.com \
--to=james.jrg@gmail.com \
--cc=chris@bubblescope.net \
--cc=gcc-help@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: link
Be 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).