public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/36690] [4.3/4.4 Regression] .debug_line first line is behind the first instruction
Date: Tue, 01 Jul 2008 15:53:00 -0000	[thread overview]
Message-ID: <20080701155234.31887.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36690-12292@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from jsm28 at gcc dot gnu dot org  2008-07-01 15:52 -------
I've also observed this problem (as causing a number of GDB testsuite
failures).

With both 4.2 and 4.3, the function prologue is followed by a jump,
the loop body, and then the test of the loop condition which the jump
jumps to.  The loop body has the correct line number, as does the
condition.  With 4.2, the jump has the same line number as the
condition, so that's the line number to which GDB assigns a breakpoint
on the function.  With 4.3, the jump insn does not have a line number
and GDB decides to use the line number of the loop body, and the GDB
tests fail.


-- 

jsm28 at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2008-07-01 15:52:34
               date|                            |
            Summary|.debug_line first line is   |[4.3/4.4 Regression]
                   |behind the first instruction|.debug_line first line is
                   |                            |behind the first instruction
   Target Milestone|---                         |4.3.2


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


  reply	other threads:[~2008-07-01 15:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 15:35 [Bug debug/36690] New: " jan dot kratochvil at redhat dot com
2008-07-01 15:53 ` jsm28 at gcc dot gnu dot org [this message]
2008-07-02  9:23 ` [Bug debug/36690] [4.3/4.4 Regression] " jakub at gcc dot gnu dot org
2008-07-10 12:02 ` jakub at gcc dot gnu dot org
2008-07-10 13:44 ` hubicka at ucw dot cz
2008-07-10 14:28 ` rguenth at gcc dot gnu dot org
2008-08-27 22:13 ` jsm28 at gcc dot gnu dot org
2008-10-03  8:56 ` jakub at gcc dot gnu dot org
2008-10-07 18:51 ` jakub at gcc dot gnu dot org
2008-10-07 19:02 ` jakub at gcc dot gnu dot org
2008-10-10  7:29 ` cnstar9988 at gmail dot com
2008-11-21 23:49 ` pinskia 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=20080701155234.31887.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).