public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jeff Sturm <jsturm@one-point.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: java/8260: gcj -fprofile-arcs -ftest-coverage doesn't work Date: Thu, 17 Oct 2002 12:46:00 -0000 [thread overview] Message-ID: <20021017194602.14376.qmail@sources.redhat.com> (raw) The following reply was made to PR java/8260; it has been noted by GNATS. From: Jeff Sturm <jsturm@one-point.com> To: owen@schwartz-omalley.com Cc: gcc-gnats@gcc.gnu.org, <gcc-prs@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <java-prs@gcc.gnu.org> Subject: Re: java/8260: gcj -fprofile-arcs -ftest-coverage doesn't work Date: Thu, 17 Oct 2002 15:42:02 -0400 (EDT) On 17 Oct 2002 owen@schwartz-omalley.com wrote: > gcj doesn't seem to support -fprofile-arcs: > > gcj -fprofile-arcs -ftest-coverage -g --main=test test.java > test.java: > Internal compiler error: Error reporting routines re-entered. > Please submit a full bug report, > with preprocessed source if appropriate. > See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. -fprofile-arcs is broken because the gcj frontend doesn't initialize long_integer_type_node. I've been using the following workaround, but haven't submitted since I'm not sure it's the right thing to do. (I.e. is int_type_node or long_type_node the correct size for it? These are java types, not C types.) Index: decl.c =================================================================== RCS file: /cvs/gcc/gcc/gcc/java/decl.c,v retrieving revision 1.132 diff -u -r1.132 decl.c --- decl.c 21 Sep 2002 02:19:44 -0000 1.132 +++ decl.c 17 Oct 2002 19:36:43 -0000 @@ -426,7 +426,7 @@ pushdecl (build_decl (TYPE_DECL, get_identifier ("byte"), byte_type_node)); short_type_node = make_signed_type (16); pushdecl (build_decl (TYPE_DECL, get_identifier ("short"), short_type_node)); - int_type_node = make_signed_type (32); + long_integer_type_node = int_type_node = make_signed_type (32); pushdecl (build_decl (TYPE_DECL, get_identifier ("int"), int_type_node)); long_type_node = make_signed_type (64); pushdecl (build_decl (TYPE_DECL, get_identifier ("long"), long_type_node));
next reply other threads:[~2002-10-17 19:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-17 12:46 Jeff Sturm [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-17 10:06 owen
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=20021017194602.14376.qmail@sources.redhat.com \ --to=jsturm@one-point.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).