public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/52384] PR16923 execution test fails
Date: Sun, 26 Feb 2012 02:16:00 -0000 [thread overview]
Message-ID: <bug-52384-8172-tmBfmCcVMY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52384-8172@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52384
--- Comment #2 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-02-26 02:16:09 UTC ---
(In reply to comment #1)
> Seems to be caused by some commit after r174664 but by r175063.
The only java related commits in this range are...
r174747 | rguenth | 2011-06-07 10:34:02 -0400 (Tue, 07 Jun 2011) | 6 lines
2011-06-07 Richard Guenther <rguenther@suse.de>
* decl.c (java_init_decl_processing): Call build_common_nodes,
build_common_nodes_2 at the beginning. Remove then duplicate
initializations.
------------------------------------------------------------------------
r174743 | rguenth | 2011-06-07 09:01:27 -0400 (Tue, 07 Jun 2011) | 29 lines
2011-06-07 Richard Guenther <rguenther@suse.de>
* tree.c (build_common_tree_nodes): Also initialize size_type_node.
Call set_sizetype from here.
c-family/
* c-common.c (c_common_nodes_and_builtins): Do not set
size_type_node or call set_sizetype.
go/
* go-lang.c (go_langhook_init): Do not set
size_type_node or call set_sizetype.
fortran/
* f95-lang.c (gfc_init_decl_processing): Do not set
size_type_node or call set_sizetype.
java/
* decl.c (java_init_decl_processing): Properly initialize
size_type_node.
lto/
* lto-lang.c (lto_init): Do not set
size_type_node or call set_sizetype.
ada/
* gcc-interface/misc.c (gnat_init): Do not set
size_type_node or call set_sizetype.
prev parent reply other threads:[~2012-02-26 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 23:52 [Bug java/52384] New: " howarth at nitro dot med.uc.edu
2012-02-26 1:56 ` [Bug java/52384] " howarth at nitro dot med.uc.edu
2012-02-26 2:16 ` howarth at nitro dot med.uc.edu [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=bug-52384-8172-tmBfmCcVMY@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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).