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 target/14907] bogus sign/zero extension when relaying parameters with regparm
Date: Sat, 10 Apr 2004 15:48:00 -0000	[thread overview]
Message-ID: <20040410153154.4557.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040410140503.14907.cesarb@nitnet.com.br>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-04-10 15:31 -------
Confirmed.  I think this is requied by the ABI to promote it but since it is already promoted it could just 
use the full register, I do not know if this is really a bug but then again I could be wrong.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
          Component|optimization                |target
     Ever Confirmed|                            |1
           Keywords|                            |pessimizes-code
   Last reconfirmed|0000-00-00 00:00:00         |2004-04-10 15:31:46
               date|                            |


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


  reply	other threads:[~2004-04-10 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10 14:59 [Bug optimization/14907] New: " cesarb at nitnet dot com dot br
2004-04-10 15:48 ` pinskia at gcc dot gnu dot org [this message]
2004-04-10 18:13 ` [Bug optimization/14907] " cesarb at nitnet dot com dot br
2004-07-10  1:28 ` [Bug target/14907] " pinskia at gcc dot gnu dot org
     [not found] <bug-14907-1037@http.gcc.gnu.org/bugzilla/>
2006-03-01  5:54 ` nmiell at comcast dot net

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=20040410153154.4557.qmail@sources.redhat.com \
    --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).