public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/50299] entryval: bigendian 32bit->64bit extension breaks address match
Date: Mon, 12 Sep 2011 16:18:00 -0000	[thread overview]
Message-ID: <bug-50299-4-8pLDznA2Cn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50299-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-09-12 15:49:43 UTC ---
Author: jakub
Date: Mon Sep 12 15:49:38 2011
New Revision: 178784

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=178784
Log:
    PR debug/50299
    * calls.c (load_register_parameters): Use use_reg_mode instead
    of use_reg when adding a single register CALL_INSN_FUNCTION_USAGE
    entry.
    (expand_call): Set EXPR_LIST mode to TYPE_MODE of the argument
    for stack CALL_INSN_FUNCTION_USAGE uses.
    * expr.h (use_reg_mode): New prototype.
    (use_reg): Changed into inline around use_reg_mode.
    * expr.c (use_reg): Renamed to...
    (use_reg_mode): ... this.  Added MODE argument, set EXPR_LIST
    mode to that mode instead of VOIDmode.
    * var-tracking.c (prepare_call_arguments): Don't track parameters
    whose EXPR_LIST mode is VOIDmode, BLKmode or X mode isn't convertible
    to it using lowpart_subreg.  Convert VALUE and REG/MEM to the
    EXPR_LIST mode.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/calls.c
    trunk/gcc/expr.c
    trunk/gcc/expr.h
    trunk/gcc/var-tracking.c


  parent reply	other threads:[~2011-09-12 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-05 18:13 [Bug debug/50299] New: " jan.kratochvil at redhat dot com
2011-09-05 18:33 ` [Bug debug/50299] " jakub at gcc dot gnu.org
2011-09-06 11:22 ` jakub at gcc dot gnu.org
2011-09-07 11:07 ` jan.kratochvil at redhat dot com
2011-09-12 16:18 ` jakub at gcc dot gnu.org [this message]
2011-09-12 16:39 ` jakub at gcc dot gnu.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=bug-50299-4-8pLDznA2Cn@http.gcc.gnu.org/bugzilla/ \
    --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).