public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/19327] [4.0 Regression] FAIL: gcc.c-torture/execute/921215-1.c compilation,  -O3 -g
Date: Mon, 17 Jan 2005 12:54:00 -0000	[thread overview]
Message-ID: <20050117125446.8402.qmail@sourceware.org> (raw)
In-Reply-To: <20050108172153.19327.danglin@gcc.gnu.org>


------- Additional Comments From ebotcazou at gcc dot gnu dot org  2005-01-17 12:54 -------
It's

2005-01-03  Daniel Berlin  <dberlin@dberlin.org>

	Fix PR debug/17924
	Fix PR debug/19191
	* dwarf2out.c (block_ultimate_origin): Follow decl origin if origin
	is a decl.
	* gimple-low.c (mark_blocks_with_used_vars): New function.
	(mark_blocks_with_used_subblocks): Ditto.
	(mark_used_blocks): Ditto.
	(pass_mark_used_blocks): New pass.
	* tree-inline.c: Include debug.h.
	(expand_call_inline): Call outlining_inline_function here.
	* tree-optimize.c (init_tree_optimization_passes): Add
	pass_mark_used_blocks. 
	* tree-pass.h (pass_mark_used_blocks): New.
	* Makefile.in (tree-inline.o): Add debug.h dependency.

The DBX back-end is now asked to output debug info for the inlined instance of
the nested function r in

main()
{
#ifndef NO_TRAMPOLINES
  void p(void ((*f) (void ())))
    {
      void r()
	{
	  foo ();
	}

      f(r);
    }

  void q(void ((*f)()))
    {
      f();
    }

  p(q);
#endif
  exit(0);
}

which is created when p is inlined.  I think it doesn't support that.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|middle-end                  |debug


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


  parent reply	other threads:[~2005-01-17 12:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08 17:22 [Bug tree-optimization/19327] New: " danglin at gcc dot gnu dot org
2005-01-08 17:26 ` [Bug middle-end/19327] " pinskia at gcc dot gnu dot org
2005-01-09 16:01 ` ebotcazou at gcc dot gnu dot org
2005-01-10  4:32 ` pinskia at gcc dot gnu dot org
2005-01-15 18:19 ` pinskia at gcc dot gnu dot org
2005-01-17  9:37 ` ebotcazou at gcc dot gnu dot org
2005-01-17 12:54 ` ebotcazou at gcc dot gnu dot org [this message]
2005-01-18  1:28 ` [Bug debug/19327] [4.0 Regression] gcc.c-torture/execute/921215-1.c compilation " dberlin at gcc dot gnu dot org
2005-01-18  1:32 ` dave at hiauly1 dot hia dot nrc dot ca
2005-01-18  2:00 ` dberlin at dberlin dot org
2005-01-18  5:23 ` ebotcazou at gcc dot gnu dot org
2005-02-08  0:30 ` mmitchel at gcc dot gnu dot org
2005-02-08  1:14 ` dberlin at gcc dot gnu dot org
2005-02-08  3:12 ` cvs-commit at gcc dot gnu dot org
2005-02-08  3:18 ` ebotcazou 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=20050117125446.8402.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).