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/45103] DW_OP_reg* has too large valid range for noreturn funcs
Date: Wed, 28 Jul 2010 10:03:00 -0000	[thread overview]
Message-ID: <20100728100333.14116.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45103-12292@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from jakub at gcc dot gnu dot org  2010-07-28 10:03 -------
Created an attachment (id=21332)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21332&action=view)
gcc46-pr45103.patch

For noreturn calls that end the function we were ignoring even
NOTE_DURING_CALL_P notes, thinking they don't affect any instructions.
While they don't affect any instructions in the current function, they affect
instructions in the called function.


-- 

jakub at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |jakub at gcc dot gnu dot org
                   |dot org                     |
             Status|UNCONFIRMED                 |ASSIGNED


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


  parent reply	other threads:[~2010-07-28 10:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28  9:54 [Bug debug/45103] New: " jan dot kratochvil at redhat dot com
2010-07-28  9:55 ` [Bug debug/45103] " jan dot kratochvil at redhat dot com
2010-07-28 10:03 ` jakub at gcc dot gnu dot org [this message]
2010-07-28 17:00 ` jakub at gcc dot gnu dot org
2010-09-07 22:46 ` 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=20100728100333.14116.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).