From: Michael Eager <eager@eagerm.com>
To: Richard Henderson <rth@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
gcc-patches@gcc.gnu.org, Jason Merrill <jason@redhat.com>,
Tom Tromey <tromey@redhat.com>,
Jan Kratochvil <jkratoch@redhat.com>,
Cary Coutant <ccoutant@google.com>,
Mark Wielaard <mjw@redhat.com>
Subject: Re: [RFC] More compact (100x) -g3 .debug_gnu_macro (take 4)
Date: Sat, 23 Jul 2011 00:32:00 -0000 [thread overview]
Message-ID: <4E2A0484.2060300@eagerm.com> (raw)
In-Reply-To: <4E29E9B9.6050606@redhat.com>
On 07/22/2011 02:20 PM, Richard Henderson wrote:
> On 07/22/2011 02:16 PM, Michael Eager wrote:
>> On 07/22/2011 02:08 PM, Richard Henderson wrote:
>>> On 07/22/2011 12:54 PM, Michael Eager wrote:
>>>> The definition of opcodes in the line number table is different from
>>>> opcodes in other tables, including a modified macro table. There
>>>> are many opcodes (essentially every possible value is used) and the
>>>> specific meaning of the opcodes may be different for different targets.
>>>
>>> I'm referring to the standard_opcode_lengths section of the .debug_line
>>> header here. We're trying to do something similar for the .debug_macro
>>> section.
>>
>> There doesn't seem to be any need. standard_opcode_lengths is only needed
>> because the opcode meanings can vary for different targets.
>
> I beg your pardon, but no, the meanings of the *standard* opcodes
> cannot vary. Only the special opcode meanings vary.
>
> See 6.2.4 #10:
>
> # By increasing opcode_base, and adding elements to this array,
> # new standard opcodes can be added, while allowing consumers who
> # do not know about these new opcodes to be able to skip them.
Which part of "not needed" did you misunderstand?
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2011-07-22 23:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 17:12 [RFC] More compact (100x) -g3 .debug_macinfo Jakub Jelinek
2011-07-13 19:59 ` Tom Tromey
2011-07-13 20:37 ` Jakub Jelinek
2011-07-18 15:42 ` Tom Tromey
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 [this message]
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=4E2A0484.2060300@eagerm.com \
--to=eager@eagerm.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=rth@redhat.com \
--cc=tromey@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).