public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/15576] Class initialization optimization is disabled
Date: Sat, 22 May 2004 20:47:00 -0000	[thread overview]
Message-ID: <20040521211917.13737.qmail@sourceware.org> (raw)
In-Reply-To: <20040521210313.15576.mckinlay@redhat.com>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-05-21 21:19 -------
Confirmed, could we make another attribute which says that it only touches the memory passed into 
the function and it is okay to remove if the agruments are the same as it will not do anything else, this 
will also help fortran's "pure" functions too.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2004-05-21 21:19:17
               date|                            |


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


  reply	other threads:[~2004-05-21 21:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-22 19:57 [Bug java/15576] New: " mckinlay at redhat dot com
2004-05-22 20:47 ` pinskia at gcc dot gnu dot org [this message]
2004-05-22 20:55 ` [Bug java/15576] " mckinlay at redhat dot com
2004-05-26 17:11 ` [Bug java/15576] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-07-09 16:51 ` pinskia at gcc dot gnu dot org
2004-11-05  0:43 ` [Bug java/15576] [4.0 " pinskia at gcc dot gnu dot org
2004-11-05  1:08 ` pinskia at gcc dot gnu dot org
2004-11-06  3:05 ` pinskia at gcc dot gnu dot org
2004-11-09 14:34 ` cvs-commit at gcc dot gnu dot org
2004-11-09 14:37 ` pinskia at gcc dot gnu 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=20040521211917.13737.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).