public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pinskia@physics.uc.edu To: gcc-gnats@gcc.gnu.org Subject: optimization/10837: noreturn attribute causes no sibling calling optimization Date: Sat, 17 May 2003 17:16:00 -0000 [thread overview] Message-ID: <20030517171222.24984.qmail@sources.redhat.com> (raw) >Number: 10837 >Category: optimization >Synopsis: noreturn attribute causes no sibling calling optimization >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sat May 17 17:16:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Andrew Pinski >Release: GNU C version 3.4 20030516 and GNU C version 3.4 20030517 >Organization: >Environment: powerpc-apple-darwin6.6 and i686-pc-linux-gnu >Description: noreturn attribute on a function causes sibling calling optimization not to be able to be done, so it causes more code to be executed then needed. >How-To-Repeat: cat >tt.c <<EOF void temp() { abort(); } void temp2() __attribute__((__noreturn__)); void temp1() { temp2(); } void temp3(); void temp4() { temp3(); } EOF gcc -O3 -fomit-frame-pointer tt.c -S look at the asm and see that temp4 has the optimization but temp1 does not. >Fix: if the attrubute is on a function, act like it is a return statement also, so that the sibiling call optimization will always work with that one. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-05-17 17:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030517171222.24984.qmail@sources.redhat.com \ --to=pinskia@physics.uc.edu \ --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).