public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/14440] New: [tree-ssa] [regression] no sib calling with _Bool types Date: Fri, 05 Mar 2004 06:18:00 -0000 [thread overview] Message-ID: <20040305061854.14440.pinskia@gcc.gnu.org> (raw) Here is a regression from the mainline: _Bool t(); _Bool f(int i) { return t(); } t should be sibcalled but is not because the return type of f is really still int for some reason by the front-end (both the C and C++ front-ends, you have to #define _Bool bool for the C++ front-end to work though). -- Summary: [tree-ssa] [regression] no sib calling with _Bool types Product: gcc Version: tree-ssa Status: UNCONFIRMED Keywords: pessimizes-code Severity: normal Priority: P2 Component: optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14440
next reply other threads:[~2004-03-05 6:18 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-05 6:18 pinskia at gcc dot gnu dot org [this message] 2004-03-05 6:23 ` [Bug optimization/14440] " pinskia at gcc dot gnu dot org 2004-03-05 6:24 ` pinskia at gcc dot gnu dot org 2004-03-06 3:58 ` pinskia at gcc dot gnu dot org 2004-04-23 4:28 ` bje at gcc dot gnu dot org 2004-04-23 5:43 ` bje at gcc dot gnu dot org 2004-04-23 11:21 ` pinskia at gcc dot gnu dot org 2004-05-07 0:10 ` dann at godzilla dot ics dot uci dot edu 2004-05-07 1:21 ` pinskia at gcc dot gnu dot org 2004-05-17 15:38 ` [Bug tree-optimization/14440] [3.5 regression] " pinskia at gcc dot gnu dot org 2004-06-07 18:13 ` pinskia at gcc dot gnu dot org 2004-06-07 18:37 ` pinskia at gcc dot gnu dot org 2004-06-09 23:54 ` pinskia at gcc dot gnu dot 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=20040305061854.14440.pinskia@gcc.gnu.org \ --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).