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 middle-end/14084] Reg allocator changes REG_EXPR
Date: Mon, 09 Feb 2004 16:49:00 -0000	[thread overview]
Message-ID: <20040209164955.12852.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040209141044.14084.zlomek@gcc.gnu.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-02-09 16:49 -------
Confirmed then, the variable tracking has to do a better job as this is correct because otherwise it will 
cause wrong code to change the reg allocator not to do this as values in the register are stored no 
matter what in the widess form, see:
/* Define this macro if it is advisable to hold scalars in registers
   in a wider mode than that declared by the program.  In such cases,
   the value is constrained to be within the bounds of the declared
   type, but kept valid in the wider mode.  The signedness of the
   extension may differ from that of the type.  */

#define PROMOTE_MODE(MODE,UNSIGNEDP,TYPE)       \
  if (GET_MODE_CLASS (MODE) == MODE_INT         \
      && GET_MODE_SIZE (MODE) < UNITS_PER_WORD) \
    (MODE) = TARGET_32BIT ? SImode : DImode;

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2004-02-09 16:49:51
               date|                            |


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


  parent reply	other threads:[~2004-02-09 16:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-09 14:10 [Bug middle-end/14084] New: " zlomek at gcc dot gnu dot org
2004-02-09 14:12 ` [Bug middle-end/14084] " zlomek at gcc dot gnu dot org
2004-02-09 16:40 ` pinskia at gcc dot gnu dot org
2004-02-09 16:44 ` zlomj9am at artax dot karlin dot mff dot cuni dot cz
2004-02-09 16:49 ` pinskia at gcc dot gnu dot org [this message]
2004-02-09 17:06 ` zlomek at gcc dot gnu dot org
2004-02-14 19:46 ` [Bug middle-end/14084] Reg allocator incorrectly changes REG_OFFSET zlomek at gcc dot gnu dot org
2004-05-15 20:29 ` pinskia at gcc dot gnu dot org
2004-05-20 19:55 ` pinskia at gcc dot gnu dot org
2004-05-27 17:41 ` cvs-commit at gcc dot gnu dot org
2004-05-27 17:42 ` pinskia at gcc dot gnu dot org
2004-05-27 17:42 ` zlomek at gcc dot gnu dot org
2004-06-05 14:11 ` cvs-commit 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=20040209164955.12852.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).