From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH RFA] tree: add build_string_literal overloads
Date: Mon, 24 Oct 2022 09:21:11 -0600 [thread overview]
Message-ID: <a3e0b9d1-40a6-9fdb-cfbb-4e1462c4e8fe@gmail.com> (raw)
In-Reply-To: <20221020202053.3389227-1-jason@redhat.com>
On 10/20/22 14:20, Jason Merrill via Gcc-patches wrote:
> Tested x86_64-pc-linux-gnu, OK for trunk?
>
> -- >8 --
>
> Simplify several calls to build_string_literal by not requiring redundant
> strlen or IDENTIFIER_* in the caller.
>
> I also corrected a wrong comment on IDENTIFIER_LENGTH.
>
> gcc/ChangeLog:
>
> * tree.h (build_string_literal): New one-argument overloads that
> take tree (identifier) and const char *.
> * builtins.cc (fold_builtin_FILE)
> (fold_builtin_FUNCTION)
> * gimplify.cc (gimple_add_init_for_auto_var)
> * vtable-verify.cc (verify_bb_vtables): Simplify calls.
>
> gcc/cp/ChangeLog:
>
> * cp-gimplify.cc (fold_builtin_source_location)
> * vtable-class-hierarchy.cc (register_all_pairs): Simplify calls to
> build_string_literal.
> (build_string_from_id): Remove.
OK
jeff
prev parent reply other threads:[~2022-10-24 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 20:20 Jason Merrill
2022-10-24 15:21 ` Jeff Law [this message]
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=a3e0b9d1-40a6-9fdb-cfbb-4e1462c4e8fe@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@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).