public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nathan at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/15484] [tree-ssa] bool and short function arguments promoted to int
Date: Wed, 17 Nov 2004 13:33:00 -0000	[thread overview]
Message-ID: <20041117133309.12661.qmail@sourceware.org> (raw)
In-Reply-To: <20040517043308.15484.dann@godzilla.ics.uci.edu>


------- Additional Comments From nathan at gcc dot gnu dot org  2004-11-17 13:33 -------
The underlying ABI might require short & bool arguments to be passed as int. 
Some do, some don't.  Anyway, that's an argument marshalling issue, which is not
currently addressed at the tree level.

The cast to int has been inserted by the front end, I think C requires that.

This is a VRP issue, not an argument marshalling one.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
  BugsThisDependsOn|                            |18373


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15484


  parent reply	other threads:[~2004-11-17 13:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 19:20 [Bug tree-optimization/15484] New: " dann at godzilla dot ics dot uci dot edu
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 [this message]
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
     [not found] <bug-15484-1008@http.gcc.gnu.org/bugzilla/>
2008-11-20 23:28 ` dann at godzilla dot ics dot uci dot edu
2008-11-20 23:36 ` 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=20041117133309.12661.qmail@sourceware.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: link
Be 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).