public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gonz@ratloop.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/10409] [ARM] "__attribute__((const))" apparently not working
Date: Wed, 04 Jun 2003 07:43:00 -0000	[thread overview]
Message-ID: <20030604074326.18676.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030415035601.10409.gonz@ratloop.com>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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



------- Additional Comments From gonz@ratloop.com  2003-06-04 07:43 -------
I would expect the problem to occur with -O0, since folding pure functions is a 
common subexpression optimization, not a semantics issue.  

Regarding my previous comments about the assembly langauge, I should note that 
under GCC 3.2.3, this code:

int test(int x) {
  return pure_func(x) << 1;
}

...produces this output:

	.size	_Z8testorigi,.Lfe1-_Z8testorigi
	.align	2
	.global	_Z4testi
	.type	_Z4testi,function
_Z4testi:
	@ Function supports interworking.
	@ args = 0, pretend = 0, frame = 0
	@ frame_needed = 1, uses_anonymous_args = 0
	mov	ip, sp
	stmfd	sp!, {fp, ip, lr, pc}
	sub	fp, ip, #4
	bl	_Z9pure_funci
	mov	r0, r0, asl #1
	ldmea	fp, {fp, sp, lr}
	bx	lr

...which is nearly identical to the code you pasted, and therefore GCC 3.4 is 
doing the right thing.  If "-fomit-frame-pointer" is failing to eliminate those 
extra pushes, it is a totally unrelated bug.

Therefore, it seems your most significant finding is that powerpc-darwin is 
still has the problem.

-Pete




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2003-06-04  7:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030415035601.10409.gonz@ratloop.com>
2003-06-04  0:22 ` dhazeghi@yahoo.com
2003-06-04  6:05 ` gonz@ratloop.com
2003-06-04  6:42 ` dhazeghi@yahoo.com
2003-06-04  7:43 ` gonz@ratloop.com [this message]
2003-06-05 13:59 ` [Bug optimization/10409] " rearnsha@gcc.gnu.org
2003-06-08 16:23 ` pinskia@physics.uc.edu

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=20030604074326.18676.qmail@sources.redhat.com \
    --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).