From: Arthur Cohen <arthur.cohen@embecosm.com>
To: Guillaume Gomez <guillaume1.gomez@gmail.com>,
gcc-patches@gcc.gnu.org, jit@gcc.gnu.org,
David Malcolm <dmalcolm@redhat.com>, Antoni <bouanto@zoho.com>
Subject: Re: [PATCH] Add rvalue::get_name method (and its C equivalent)
Date: Mon, 22 Apr 2024 11:51:14 +0200 [thread overview]
Message-ID: <7346764f-bf4d-4075-8191-671201f6f8da@embecosm.com> (raw)
In-Reply-To: <CAAOQCfSYhUkt57q1DLyQkbNROOVi3GJbEFsamcY8NdqvsTw2wg@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 796 bytes --]
Hey Guillaume :)
On 4/20/24 01:05, Guillaume Gomez wrote:
> Hi,
>
> I just encountered the need to retrieve the name of an `rvalue` (if
> there is one) while working on the Rust GCC backend.
>
> This patch adds a getter to retrieve the information.
>
> Cordially.
> virtual bool get_wide_int (wide_int *) const { return false; }
>
> + virtual string * get_name () { return NULL; }
> +
> private:
> virtual enum precedence get_precedence () const = 0;
Is there any reason for that getter to return a mutable pointer to the
name? Would something like this work instead if you're just looking at
getting the name?
+ virtual string * get_name () const { return NULL; }
With of course adequate modifications to the inheriting classes.
Best,
Arthur
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3195 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2024-04-22 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 23:05 Guillaume Gomez
2024-04-22 9:51 ` Arthur Cohen [this message]
2024-04-22 13:04 ` Guillaume Gomez
2024-04-22 13:13 ` Antoni Boucher
2024-04-22 13:16 ` Guillaume Gomez
2024-04-22 13:19 ` Antoni Boucher
2024-04-22 13:24 ` Guillaume Gomez
2024-04-22 15:19 ` Antoni Boucher
2024-04-22 17:56 ` Guillaume Gomez
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=7346764f-bf4d-4075-8191-671201f6f8da@embecosm.com \
--to=arthur.cohen@embecosm.com \
--cc=bouanto@zoho.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=guillaume1.gomez@gmail.com \
--cc=jit@gcc.gnu.org \
/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).