public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dhazeghi@yahoo.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/9760] [arm] Combine cannot do its job because immediate operand is used instead of register Date: Mon, 26 May 2003 20:02:00 -0000 [thread overview] Message-ID: <20030526194939.12818.qmail@sources.redhat.com> (raw) In-Reply-To: <20030219170600.9760.beszedes@rgai.hu> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9760 ------- Additional Comments From dhazeghi@yahoo.com 2003-05-26 19:49 ------- Hello, with gcc 3.3 I get the following code: .file "01.i" .text .align 2 .global func .type func, %function func: @ args = 0, pretend = 0, frame = 0 @ frame_needed = 0, uses_anonymous_args = 0 @ link register save eliminated. @ lr needed for prologue mov pc, lr .size func, .-func .align 2 .global foo .type foo, %function foo: @ args = 0, pretend = 0, frame = 0 @ frame_needed = 1, uses_anonymous_args = 0 mov ip, sp stmfd sp!, {r4, fp, ip, lr, pc} mov r1, r0, lsr #24 sub fp, ip, #4 mov r4, r0 mov r0, #8 bl func mov r1, r4, asr #16 and r1, r1, #255 mov r0, #8 bl func mov r4, r4, asr #8 and r4, r4, #255 mov r1, r4 mov r0, #8 ldmea fp, {r4, fp, sp, lr} b func .size foo, .-foo .ident "GCC: (GNU) 3.3 20030508 (prerelease)" with mainline, I get this slightly different code: .file "01.i" .text .align 2 .global func .type func, %function func: @ args = 0, pretend = 0, frame = 0 @ frame_needed = 0, uses_anonymous_args = 0 @ link register save eliminated. @ lr needed for prologue mov pc, lr .size func, .-func .align 2 .global foo .type foo, %function foo: @ args = 0, pretend = 0, frame = 0 @ frame_needed = 1, uses_anonymous_args = 0 mov ip, sp stmfd sp!, {r4, fp, ip, lr, pc} mov r1, r0, lsr #24 sub fp, ip, #4 mov r4, r0 mov r0, #8 bl func mov r1, r4, lsr #16 and r1, r1, #255 mov r0, #8 bl func mov r4, r4, lsr #8 and r1, r4, #255 mov r0, #8 ldmea fp, {r4, fp, sp, lr} b func .size foo, .-foo .ident "GCC: (GNU) 3.4 20030508 (experimental)" Is this an improvement from the code you saw (sorry, I don't know arm asm, and there are too many changes from the .s file you provided just to do a diff)? Thanks, Dara ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next parent reply other threads:[~2003-05-26 19:56 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20030219170600.9760.beszedes@rgai.hu> 2003-05-26 20:02 ` dhazeghi@yahoo.com [this message] 2003-05-26 20:18 ` pinskia@physics.uc.edu 2003-06-02 1:18 ` pinskia@physics.uc.edu 2003-08-14 3:19 ` pinskia at gcc dot gnu dot org 2004-08-20 6:42 ` pinskia at gcc dot gnu dot org [not found] <bug-9760-5458@http.gcc.gnu.org/bugzilla/> 2009-03-12 18:45 ` ramana dot r at gmail dot com 2010-02-08 16:11 ` steven at gcc dot gnu dot org 2010-02-08 16:30 ` rearnsha at arm dot com 2010-02-08 16:31 ` rearnsha at arm dot com [not found] <bug-9760-4@http.gcc.gnu.org/bugzilla/> 2021-07-26 7:29 ` pinskia 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=20030526194939.12818.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: linkBe 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).