public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aph at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/26447] [4.2 Regression] verify_flow_info failed, load PRE with java program
Date: Wed, 03 May 2006 10:22:00 -0000	[thread overview]
Message-ID: <20060503102235.29724.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26447-511@http.gcc.gnu.org/bugzilla/>



------- Comment #18 from aph at gcc dot gnu dot org  2006-05-03 10:22 -------
gcj -findirect-dispatch doesn't work with .java files, only with .class files,
so I didn't try it.

class XMLStreamWriter 
{
  void writeCharacters(String s) {}
}

class XMLStreamException extends Exception {}

public class StAXWriter
{
  XMLStreamWriter writer;
  int indent = 0;
  public void writeEnd(boolean wasEmpty)
  {
    try
      {
        indent -= 2;
        for (int i = 0; i < indent; i++)
          writer.writeCharacters(" ");
      }
    catch (XMLStreamException xmlse)
      {
      }
  }
}


-- 


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


  parent reply	other threads:[~2006-05-03 10:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23 16:32 [Bug tree-optimization/26447] New: verify_flow_info failed aph at gcc dot gnu dot org
2006-02-23 16:34 ` [Bug tree-optimization/26447] " aph at gcc dot gnu dot org
2006-02-24 19:00 ` pinskia at gcc dot gnu dot org
2006-02-27 17:22 ` aph at gcc dot gnu dot org
2006-02-27 17:26 ` pinskia at gcc dot gnu dot org
2006-02-27 17:41 ` [Bug tree-optimization/26447] [4.2 Regression] verify_flow_info failed, load PRE pinskia at gcc dot gnu dot org
2006-02-27 17:44 ` pinskia at gcc dot gnu dot org
2006-02-27 19:46 ` dberlin at dberlin dot org
2006-02-27 20:17 ` dberlin at dberlin dot org
2006-03-02 10:31 ` aph at gcc dot gnu dot org
2006-03-06 15:24 ` pinskia at gcc dot gnu dot org
2006-05-02 15:19 ` [Bug tree-optimization/26447] [4.2 Regression] verify_flow_info failed, load PRE with java program pinskia at gcc dot gnu dot org
2006-05-02 17:32 ` mckinlay at redhat dot com
2006-05-03  8:10 ` rguenth at gcc dot gnu dot org
2006-05-03 10:00 ` rguenth at gcc dot gnu dot org
2006-05-03 10:11 ` aph at gcc dot gnu dot org
2006-05-03 10:14 ` rguenth at gcc dot gnu dot org
2006-05-03 10:22 ` aph at gcc dot gnu dot org [this message]
2006-05-03 10:37 ` rguenth at gcc dot gnu dot org
2006-05-03 12:09 ` rguenth at gcc dot gnu dot org
2006-05-04  7:45 ` rguenth at gcc dot gnu dot org
2006-05-04  7:45 ` rguenth at gcc dot gnu dot org
2006-05-15 19:32 ` patchapp at dberlin dot 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=20060503102235.29724.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).