public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Cary Coutant <ccoutant@google.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Jim Wilson <wilson@codesourcery.com>, Jason Merrill <jason@redhat.com>
Subject: Re: [patch] Add discriminators to DWARF line table
Date: Wed, 20 May 2009 18:40:00 -0000	[thread overview]
Message-ID: <c17be2b30905201139s7039ba76x7478062019856faa@mail.gmail.com> (raw)
In-Reply-To: <c17be2b30905131501w530a486ai6f585a21b7b150e3@mail.gmail.com>

Ping.

Jim or Jason, would either of you have the time to review this patch?

Current patch:

  http://gcc.gnu.org/ml/gcc-patches/2009-04/msg02388.html

Original posting with background info:

  http://gcc.gnu.org/ml/gcc-patches/2009-04/msg01679.html

-cary


	* basic-block.h (struct basic_block_def): Add discriminator field.
	* dbxout.c (dbxout_source_line): Add new parameter.  Change all
	callers.
	* debug.c (do_nothing_debug_hooks): Add additional entry.
	(debug_nothing_int_charstar_int): New function.
	* debug.h (struct gcc_debug_hooks): Add parameter to source_line
	hook.
	(debug_nothing_int_charstar_int): New declaration.
	* dwarf2out.c (dwarf2out_source_line): Add new parameter.  Write
	discriminator value in .loc directive.
	* final.c (last_discriminator): New variable.
	(discriminator): New variable.
	(final_start_function): Initialize above variables, pass current
	discriminator to debug hook.
	(notice_source_line): Check for discriminator change.
	* gimple-pretty-print.c (dump_bb_header): Print discriminator value.
	* sdbout.c (sdbout_source_line): New parameter.
	* tree-cfg.c (struct locus_discrim_map): New structure type.
	(discriminator_per_locus): New hash table.
	(build_gimple_cfg): Allocate and free discriminator hash table.
	(make_edges): Call assign_discriminator.
	(locus_map_hash): New function.
	(locus_map_eq): New function.
	(next_discriminator_for_locus): New function.
	(same_line_p): New function.
	(assign_discriminator): New function.
	(make_cond_expr_edges): Call assign_discriminator.
	(make_gimple_switch_edges): Likewise.
	(first_non_label_stmt): New function.
	* vmsdbgout.c (vmsdbgout_source_line): Add new parameter.  Change
	all callers.
	* xcoffout.c (xcoffout_source_line): Add new parameter.

	* configure.ac (gcc_cv_as_discriminator): New configury check for
	gas support for discriminator.
	* configure: Regenerate.
	* config.in: Regenerate.

  reply	other threads:[~2009-05-20 18:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 22:01 [ping] " Cary Coutant
2009-05-20 18:40 ` Cary Coutant [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-05 18:01 [patch] " David Edelsohn
2009-04-21 23:16 Cary Coutant
2009-04-22  4:19 ` Daniel Jacobowitz
2009-04-22 18:05   ` Cary Coutant
2009-04-23  0:39     ` Cary Coutant
2009-04-30  0:54       ` Cary Coutant
2009-06-02 20:38         ` Diego Novillo
2009-06-02 21:02           ` Cary Coutant
2009-06-03  1:03             ` Cary Coutant
2009-06-03 11:44               ` Diego Novillo
2009-06-03 14:26               ` Tom Tromey
2009-06-03 15:15                 ` Diego Novillo
2009-06-03 18:47                   ` Cary Coutant
2009-06-04 22:27                     ` Cary Coutant

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=c17be2b30905201139s7039ba76x7478062019856faa@mail.gmail.com \
    --to=ccoutant@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=wilson@codesourcery.com \
    /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).