public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: fshvaige@cisco.com To: gcc-gnats@gcc.gnu.org Subject: optimization/7005: Sibling and tail recursive calls optimisation with -fomit-frame-pointer: strange code generated. Date: Wed, 12 Jun 2002 06:16:00 -0000 [thread overview] Message-ID: <20020612131331.2621.qmail@sources.redhat.com> (raw) >Number: 7005 >Category: optimization >Synopsis: Sibling and tail recursive calls optimisation with -fomit-frame-pointer: strange code generated. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: pessimizes-code >Submitter-Id: net >Arrival-Date: Wed Jun 12 06:16:04 PDT 2002 >Closed-Date: >Last-Modified: >Originator: fshvaige@cisco.com >Release: 3.1 and 3.1 20020510 (prerelease) >Organization: >Environment: >Description: File test2.c: int f1 (void); int f2 (void) { return f1 (); } i686 -Os (best code): f2: jmp f1 i686 -O2/-O3 (Ooops): f2: subl $12, %esp addl $12, %esp jmp f1 PowerPC -Os/-O2/-O3 (Ooops): f2: stwu 1,-8(1) mflr 0 stw 0,12(1) bl f1 lwz 0,12(1) addi 1,1,8 mtlr 0 blr >How-To-Repeat: gcc -S -Os test2.c -Wall -fomit-frame-pointer gcc -S -O2 test2.c -Wall -fomit-frame-pointer gcc -S -O3 test2.c -Wall -fomit-frame-pointer ppc-eabi-gcc -S -Os test2.c -Wall -fomit-frame-pointer ppc-eabi-gcc -S -O2 test2.c -Wall -fomit-frame-pointer ppc-eabi-gcc -S -O3 test2.c -Wall -fomit-frame-pointer >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-06-12 13:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-12 6:16 fshvaige [this message] 2002-06-12 6:46 Andrew Pinski 2002-06-14 16:35 rth
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=20020612131331.2621.qmail@sources.redhat.com \ --to=fshvaige@cisco.com \ --cc=gcc-gnats@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).