From: Keith Seitz <keiths@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH 9/9] C++ compile support
Date: Wed, 24 Mar 2021 07:51:56 -0700 [thread overview]
Message-ID: <226bae37-cd78-69e6-17d8-8450690b7b73@redhat.com> (raw)
In-Reply-To: <e56af935-5487-b051-0550-c1d0e8b9c47e@polymtl.ca>
On 3/23/21 6:04 PM, Simon Marchi wrote:
> Hi Keith,
>
> I am from the past...
Hahaha... That's okay; I feel like I am living in the past!
> On 2018-08-10 7:25 p.m., Keith Seitz wrote:
>> + gcc_decl resuld;
>> + if (TYPE_CODE (type) == TYPE_CODE_STRUCT)
>> + {
>> + const char *what = TYPE_DECLARED_CLASS (type) ? "struct" : "class";
>
> I don't know if this matters, but the condition above looks reversed,
> can you confirm?
Wowser. Good catch!
While it should *of course* be corrected, the first parameter there is
essentially for debugging, so it is not critical that this be propagated
everywhere:
gcc_expr build_decl (const char *debug_decltype, const char *name,
enum gcc_cp_symbol_kind sym_kind, gcc_type sym_type,
const char *substitution_name, gcc_address address,
const char *filename, unsigned int line_number);
Let me know if you want me to clean up my boo-boo or whether you've
patch-in-hand to push already.
Keith
next prev parent reply other threads:[~2021-03-24 14:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 23:25 [PATCH 0/9] C++ Support for Compile Keith Seitz
2018-08-10 23:25 ` [PATCH 3/9] Change `label_symbols' to std::vector in linespec.c structures Keith Seitz
2018-08-11 14:50 ` Tom Tromey
2018-08-10 23:25 ` [PATCH 2/9] Change `function_symbols' to std::vector Keith Seitz
2018-08-11 14:49 ` Tom Tromey
2018-08-17 17:59 ` Keith Seitz
2018-08-28 17:43 ` Tom Tromey
2018-08-10 23:25 ` [PATCH 1/9] Change `file_symtabs' " Keith Seitz
2018-08-11 14:47 ` Tom Tromey
2018-08-17 17:56 ` Keith Seitz
2018-08-28 17:30 ` Tom Tromey
2018-08-10 23:31 ` [PATCH 6/9] Remove VEC definitions from linespec.c Keith Seitz
2018-08-11 15:03 ` Tom Tromey
2018-08-10 23:31 ` [PATCH 7/9] Use block_symbol_d in linespec APIs Keith Seitz
2018-08-11 15:05 ` Tom Tromey
2018-08-17 18:04 ` Keith Seitz
2018-08-10 23:32 ` [PATCH 4/9] Change `minimal_symbols' to std::vector in linespec.c structures Keith Seitz
2018-08-11 15:01 ` Tom Tromey
2018-08-17 18:00 ` Keith Seitz
2018-08-28 17:44 ` Tom Tromey
2018-08-10 23:32 ` [PATCH 9/9] C++ compile support Keith Seitz
2018-08-11 7:22 ` Eli Zaretskii
2018-08-17 17:51 ` Keith Seitz
2018-08-17 18:57 ` Eli Zaretskii
2018-08-20 17:02 ` Keith Seitz
2018-08-12 0:17 ` Tom Tromey
2018-08-17 18:26 ` Keith Seitz
2018-08-28 17:52 ` Tom Tromey
2018-08-29 22:32 ` Keith Seitz
2021-03-24 1:04 ` Simon Marchi
2021-03-24 14:51 ` Keith Seitz [this message]
2021-03-24 15:06 ` Simon Marchi
2021-03-24 20:49 ` Keith Seitz
2021-04-01 18:03 ` Tom Tromey
2021-04-01 18:07 ` Luis Machado
2021-04-01 19:36 ` Keith Seitz
2018-08-10 23:32 ` [PATCH 5/9] Change decode_compound_collector to use std::vector Keith Seitz
2018-08-11 15:02 ` Tom Tromey
2018-08-17 18:04 ` Keith Seitz
2018-08-20 1:20 ` Simon Marchi
2018-08-20 13:28 ` Tom Tromey
2018-08-20 14:03 ` Simon Marchi
2018-08-28 17:46 ` Tom Tromey
2018-08-10 23:34 ` [PATCH 8/9] Add new search_symbols_multiple API Keith Seitz
2018-08-11 20:49 ` 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=226bae37-cd78-69e6-17d8-8450690b7b73@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).