public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/5739: [sparc] "const" and "pure" function attributes pessimize code
Date: Sun, 11 May 2003 08:56:00 -0000	[thread overview]
Message-ID: <20030511085601.9352.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/5739; it has been noted by GNATS.

From: Dan Nicolaescu <dann@ics.uci.edu>
To: Dara Hazeghi <dhazeghi@yahoo.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: optimization/5739: [sparc] "const" and "pure" function attributes pessimize code
Date: Sun, 11 May 2003 01:52:26 -0700

 I can confirm that the problem is still present in mainline cvs. Both
 in 32 and 64-bit sparc configurations.
 
 It also occurs for x86, but the difference in generated code is much
 smaller.


             reply	other threads:[~2003-05-11  8:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-11  8:56 Dan Nicolaescu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-10 10:16 Dara Hazeghi

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=20030511085601.9352.qmail@sources.redhat.com \
    --to=dann@ics.uci.edu \
    --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: 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).