public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jason Merrill <jason@redhat.com>,
	Richard Henderson <rth@redhat.com>,
	       Jan Kratochvil <jkratoch@redhat.com>,
	       Roland McGrath <roland@redhat.com>,
	Cary Coutant <ccoutant@google.com>,
	       Mark Wielaard <mjw@redhat.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: [RFC] More compact (100x) -g3 .debug_macinfo
Date: Mon, 18 Jul 2011 15:42:00 -0000	[thread overview]
Message-ID: <m38vrv8x9s.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110713201747.GZ2687@tyan-ft48-01.lab.bos.redhat.com> (Jakub	Jelinek's message of "Wed, 13 Jul 2011 22:17:47 +0200")

>>>>> "Jakub" == Jakub Jelinek <jakub@redhat.com> writes:

Tom> I don't think I really understood DW_MACINFO_GNU_define_opcode, so the
Tom> implementation here is probably wrong.

Jakub> Well, I think you've skipped it correctly and furthermore even patched
Jakub> GCC doesn't emit it.  The point of it was to allow skipping unknown
Jakub> opcodes.  If you implement this opcode fully and say GCC 4.8 adds a new
Jakub> vendor opcode, the old implementation would be able to silently skip
Jakub> over such opcodes.

I implemented this part today, so I think the gdb patch is complete now.

Tom

  reply	other threads:[~2011-07-18 14:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 17:12 Jakub Jelinek
2011-07-13 19:59 ` Tom Tromey
2011-07-13 20:37   ` Jakub Jelinek
2011-07-18 15:42     ` Tom Tromey [this message]
2011-07-15 15:52 ` [RFC] More compact (100x) -g3 .debug_macinfo (take 2) Jakub Jelinek
2011-07-15 17:19   ` Richard Henderson
2011-07-15 21:18     ` [RFC] More compact (100x) -g3 .debug_macinfo (take 3) Jakub Jelinek
2011-07-18 15:09       ` Tom Tromey
2011-07-20  1:17       ` Richard Henderson
2011-07-21 11:38         ` [RFC] More compact (100x) -g3 .debug_gnu_macro (take 4) Jakub Jelinek
2011-07-21 17:25           ` Richard Henderson
2011-07-21 18:13             ` Jakub Jelinek
2011-07-22 13:49             ` [RFC] More compact (100x) -g3 .debug_gnu_macro (take 5) Jakub Jelinek
2011-07-22 15:34               ` Tom Tromey
2011-07-22 17:24               ` Richard Henderson
2011-07-22 20:33             ` [RFC] More compact (100x) -g3 .debug_gnu_macro (take 4) Michael Eager
2011-07-22 21:50               ` Richard Henderson
2011-07-22 21:51                 ` Michael Eager
2011-07-22 22:10                   ` Richard Henderson
2011-07-23  0:32                     ` Michael Eager
2011-07-23  0:36                       ` Richard Henderson
2011-07-26  7:34                         ` Jason Merrill
2011-07-15 18:28   ` [RFC] More compact (100x) -g3 .debug_macinfo (take 2) Tom Tromey
2011-07-15 19:21     ` Jakub Jelinek
2011-07-15 19:30       ` Tom Tromey

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=m38vrv8x9s.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=ccoutant@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jason@redhat.com \
    --cc=jkratoch@redhat.com \
    --cc=mjw@redhat.com \
    --cc=roland@redhat.com \
    --cc=rth@redhat.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).