From: Jeff Law <jeffreyalaw@gmail.com>
To: Mark Harmstone <mark@harmstone.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 06/11] Handle enums for CodeView
Date: Sun, 23 Jun 2024 21:49:17 -0600 [thread overview]
Message-ID: <1e8b5fa2-3464-4eb4-bfd9-533346363d79@gmail.com> (raw)
In-Reply-To: <20240618001713.24034-7-mark@harmstone.com>
On 6/17/24 6:17 PM, Mark Harmstone wrote:
> Translates DW_TAG_enumeration_type DIEs into LF_ENUM symbols.
>
> gcc/
> * dwarf2codeview.cc (MAX_FIELDLIST_SIZE): Define.
> (struct codeview_integer): New structure.
> (struct codeview_subtype): Likewise
> (struct codeview_custom_type): Add lf_fieldlist and lf_enum
> to union.
> (write_cv_integer, cv_integer_len): New functions.
> (write_lf_fieldlist, write_lf_enum): Likewise.
> (write_custom_types): Call write_lf_fieldlist and write_lf_enum.
> (add_enum_forward_def): New function.
> (get_type_num_enumeration_type): Likewise.
> (get_type_num): Handle DW_TAG_enumeration_type DIEs.
> * dwarf2codeview.h (LF_FIELDLIST, LF_INDEX, LF_ENUMERATE): Define.
> (LF_ENUM, LF_CHAR, LF_SHORT, LF_USHORT, LF_LONG): Likewise.
> (LF_ULONG, LF_QUADWORD, LF_UQUADWORD): Likewise.
> (CV_ACCESS_PRIVATE, CV_ACCESS_PROTECTED): Likewise.
> (CV_ACCESS_PUBLIC, CV_PROP_FWDREF): Likewise.
> ---
> gcc/dwarf2codeview.cc | 524 ++++++++++++++++++++++++++++++++++++++++++
> gcc/dwarf2codeview.h | 17 ++
> 2 files changed, 541 insertions(+)
>
> @@ -978,6 +1022,292 @@ write_lf_modifier (codeview_custom_type *t)
> asm_fprintf (asm_out_file, "%LLcv_type%x_end:\n", t->num);
> }
>
> +/* Write a CodeView extensible integer. If the value is non-negative and
> + < 0x8000, the value gets written directly as an uint16_t. Otherwise, we
> + output two bytes for the integer type (LF_CHAR, LF_SHORT, ...), and the
> + actual value follows. */
As a follow-up, can you include a brief description of the return value?
Pushed to the trunk. Thanks!
jeff
next prev parent reply other threads:[~2024-06-24 3:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 0:17 [PATCH 00/11] CodeView variables and type system Mark Harmstone
2024-06-18 0:17 ` [PATCH 01/11] Output CodeView data about variables Mark Harmstone
2024-06-23 23:50 ` Jeff Law
2024-06-18 0:17 ` [PATCH 02/11] Handle CodeView base types Mark Harmstone
2024-06-24 0:18 ` Jeff Law
2024-06-18 0:17 ` [PATCH 03/11] Handle typedefs for CodeView Mark Harmstone
2024-06-24 0:30 ` Jeff Law
2024-06-18 0:17 ` [PATCH 04/11] Handle pointers " Mark Harmstone
2024-06-24 3:31 ` Jeff Law
2024-06-18 0:17 ` [PATCH 05/11] Handle const and varible modifiers " Mark Harmstone
2024-06-24 3:39 ` Jeff Law
2024-06-25 2:49 ` Mark Harmstone
2024-06-25 5:42 ` Jeff Law
2024-06-18 0:17 ` [PATCH 06/11] Handle enums " Mark Harmstone
2024-06-24 3:49 ` Jeff Law [this message]
2024-06-18 0:17 ` [PATCH 07/11] Handle structs and classes " Mark Harmstone
2024-06-25 5:40 ` Jeff Law
2024-06-18 0:17 ` [PATCH 08/11] Handle unions " Mark Harmstone
2024-06-25 23:29 ` Jeff Law
2024-06-18 0:17 ` [PATCH 09/11] Handle arrays " Mark Harmstone
2024-06-25 23:32 ` Jeff Law
2024-06-18 0:17 ` [PATCH 10/11] Handle bitfields " Mark Harmstone
2024-06-26 2:21 ` Jeff Law
2024-06-18 0:17 ` [PATCH 11/11] Handle subroutine types in CodeView Mark Harmstone
2024-06-26 2:27 ` Jeff Law
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=1e8b5fa2-3464-4eb4-bfd9-533346363d79@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mark@harmstone.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).