public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "aph at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/64044] Java emits bogus .class$ decls
Date: Mon, 24 Nov 2014 11:28:00 -0000	[thread overview]
Message-ID: <bug-64044-8172-KDCyRXxPBl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64044-8172@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64044

--- Comment #5 from Andrew Haley <aph at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #4)
> On Mon, 24 Nov 2014, aph at redhat dot com wrote:
> 
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64044
> > 
> > Andrew Haley <aph at redhat dot com> changed:
> > 
> >            What    |Removed                     |Added
> > ----------------------------------------------------------------------------
> >                  CC|                            |aph at redhat dot com
> > 
> > --- Comment #2 from Andrew Haley <aph at redhat dot com> ---
> > So, is the solution to this trivially not to mark the .class$ decls as
> > TREE_CONST ?
> 
> Yes, see the patch I proposed (in testing right now, I'll post it
> and ask for approval later today unless you want to pre-approve here)

Fine by me.  I did that because I wanted some way to tell GCC that it could
treat the field as readonly, but TREE_CONST doesn't do that.


  parent reply	other threads:[~2014-11-24 11:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 10:32 [Bug java/64044] New: " rguenth at gcc dot gnu.org
2014-11-24 10:35 ` [Bug java/64044] " rguenth at gcc dot gnu.org
2014-11-24 10:38 ` aph at redhat dot com
2014-11-24 10:39 ` rguenth at gcc dot gnu.org
2014-11-24 10:50 ` rguenther at suse dot de
2014-11-24 11:28 ` aph at gcc dot gnu.org [this message]
2014-11-24 14:02 ` rguenth at gcc dot gnu.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=bug-64044-8172-KDCyRXxPBl@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).