public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "t66667 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/42489] Opt bug -foptimize-sibling-calls function call stalled! dead-lock, cpu max
Date: Fri, 25 Dec 2009 02:52:00 -0000	[thread overview]
Message-ID: <20091225025156.24905.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42489-18091@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from t66667 at gmail dot com  2009-12-25 02:51 -------
No simple test-case code can be provided you have to read libxml2 source
error.c about less then 1000 lines.
Without running program in the gdb, fprintf to stderr in the beginning of the
__xmlRaiseError() there was no output, ran in gdb there was output and
dead-lock cpu running 100% & it contributes to global warming.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42489


  parent reply	other threads:[~2009-12-25  2:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-24 11:43 [Bug rtl-optimization/42489] New: Function call never happened after compile with -foptimize-sibling-calls t66667 at gmail dot com
2009-12-24 11:44 ` [Bug rtl-optimization/42489] " t66667 at gmail dot com
2009-12-24 11:57 ` t66667 at gmail dot com
2009-12-24 21:25 ` d dot g dot gorbachev at gmail dot com
2009-12-24 21:30 ` t66667 at gmail dot com
2009-12-24 22:09 ` t66667 at gmail dot com
2009-12-24 22:45 ` t66667 at gmail dot com
2009-12-25  1:19 ` paolo dot carlini at oracle dot com
2009-12-25  2:46 ` [Bug rtl-optimization/42489] Opt bug -foptimize-sibling-calls function call stalled! dead-lock, cpu max t66667 at gmail dot com
2009-12-25  2:52 ` t66667 at gmail dot com [this message]
2009-12-25  9:19 ` t66667 at gmail dot com
2009-12-25 13:34 ` d dot g dot gorbachev at gmail dot com
2010-01-05 11:14 ` t66667 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=20091225025156.24905.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: 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).