public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/55257] [4.8 Regression]: g++.dg/debug/dwarf2/non-virtual-thunk.C scan-assembler thunk.C:30
Date: Mon, 12 Nov 2012 17:08:00 -0000	[thread overview]
Message-ID: <bug-55257-4-gw5XrLTXQY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55257-4@http.gcc.gnu.org/bugzilla/>


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

Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2012-11-12
         AssignedTo|unassigned at gcc dot       |hp at gcc dot gnu.org
                   |gnu.org                     |
   Target Milestone|---                         |4.8.0
     Ever Confirmed|0                           |1

--- Comment #2 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2012-11-12 17:08:12 UTC ---
(In reply to comment #1)
> If the target doesn't call final_start_function and final_end_function in
> output_mi_thunk targhook (or equivalent), it is a target bug.

I see.  I either missed this requirement when I implemented those bits for CRIS
or it wasn't a requirement at the time.  BTW, I see several ports are missing
those calls.  I guess in the general case it can't be left to middle-end to
call those functions at the right time, so I'll just update the port and
hopefully the documentation, but no promises.  Assigning the PR to myself while
verifying that this is the cause.


  parent reply	other threads:[~2012-11-12 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-10  1:52 [Bug debug/55257] New: " hp at gcc dot gnu.org
2012-11-12  7:51 ` [Bug debug/55257] " jakub at gcc dot gnu.org
2012-11-12 17:08 ` hp at gcc dot gnu.org [this message]
2012-11-12 17:15 ` jakub at gcc dot gnu.org
2012-11-12 17:22 ` hp at gcc dot gnu.org
2012-11-13  6:14 ` [Bug target/55257] " hp at gcc dot gnu.org
2012-11-13  6:16 ` hp at gcc dot gnu.org
2012-11-13  6:39 ` hp 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-55257-4-gw5XrLTXQY@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).