public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dann at godzilla dot ics dot uci dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/15484] New: [tree-ssa] bool and short function arguments promoted to int Date: Mon, 17 May 2004 19:20:00 -0000 [thread overview] Message-ID: <20040517043308.15484.dann@godzilla.ics.uci.edu> (raw) This code: _Bool bar (_Bool a); _Bool foo1 (_Bool a) { if (bar(a)) return 1; else return 0; } static short barshort (short a); short foo1short (short a) { if (barshort(a)) return 1; else return 0; } is transformed to: (when using -O -fdump-tree-generic) foo1 (a) { int T.17; _Bool T.18; T.17 = (int)a; <------ this is not needed T.18 = bar (T.17); if (T.18 != 0) { return 1; } else { return 0; } } foo1short (a) { int T.19; short int T.20; T.19 = (int)a; <------ this is not needed T.20 = barshort (T.19); if (T.20 != 0) { return 1; } else { return 0; } } the promotions shown are not needed, at least not at this point in the compilation process. -- Summary: [tree-ssa] bool and short function arguments promoted to int Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: dann at godzilla dot ics dot uci dot edu CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15484
next reply other threads:[~2004-05-17 4:33 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-05-17 19:20 dann at godzilla dot ics dot uci dot edu [this message] 2004-05-17 19:22 ` [Bug tree-optimization/15484] " pinskia at gcc dot gnu dot org 2004-11-17 13:33 ` nathan at gcc dot gnu dot org 2004-12-29 1:33 ` dann at godzilla dot ics dot uci dot edu 2005-05-16 13:55 ` rguenth at gcc dot gnu dot org 2005-06-02 18:44 ` dnovillo 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=20040517043308.15484.dann@godzilla.ics.uci.edu \ --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).