public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/45003] VTA issues with sign/zero extension and debug temporaries
Date: Wed, 21 Jul 2010 08:51:00 -0000	[thread overview]
Message-ID: <20100721085117.14829.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45003-87@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from jakub at gcc dot gnu dot org  2010-07-21 08:51 -------
Subject: Bug 45003

Author: jakub
Date: Wed Jul 21 08:50:57 2010
New Revision: 162364

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=162364
Log:
        PR debug/45003
        * var-tracking.c (reverse_op): Also handle {SIGN,ZERO}_EXTEND of
        a MEM.
        * dwarf2out.c (loc_descriptor): Don't handle SIGN_EXTEND nor
        ZERO_EXTEND here.

        * gcc.dg/guality/pr45003-2.c: New test.
        * gcc.dg/guality/pr45003-3.c: New test.

Added:
    trunk/gcc/testsuite/gcc.dg/guality/pr45003-2.c
    trunk/gcc/testsuite/gcc.dg/guality/pr45003-3.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/dwarf2out.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/var-tracking.c


-- 


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


  parent reply	other threads:[~2010-07-21  8:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 10:31 [Bug ada/45003] New: " jakub at gcc dot gnu dot org
2010-07-20 10:40 ` [Bug ada/45003] " jakub at gcc dot gnu dot org
2010-07-20 10:42 ` jakub at gcc dot gnu dot org
2010-07-20 12:58 ` jakub at gcc dot gnu dot org
2010-07-20 16:27 ` [Bug debug/45003] " jakub at gcc dot gnu dot org
2010-07-21  8:51 ` jakub at gcc dot gnu dot org [this message]
2010-07-21  8:59 ` jakub 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=20100721085117.14829.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).