public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/105863] RFE: C23 #embed
Date: Thu, 16 May 2024 20:41:09 +0000	[thread overview]
Message-ID: <bug-105863-4-wpcX2wX84E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105863-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105863

--- Comment #9 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
The most straightforward and most important case to optimize is the one where
the #embed expansion lies entirely inside a single character array initializer
(possibly with some integer constants before or after it in the initializer -
whether coming from the prefix and suffix parameters to #embed or otherwise) -
in which case the initializer can be converted internally to a STRING_CST.
Cases that aren't within a character array initializer like that are harder to
optimize (might require additional internal representation beyond the front
end), and probably also less important to optimize initially.

  parent reply	other threads:[~2024-05-16 20:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 16:52 [Bug c/105863] New: RFE: __attribute__((incbin("file"))) or __builtin_incbin("file") hpa at zytor dot com
2022-06-06 17:36 ` [Bug c/105863] " pinskia at gcc dot gnu.org
2022-06-06 17:43 ` amonakov at gcc dot gnu.org
2022-06-13 12:59 ` rguenth at gcc dot gnu.org
2023-06-05 19:55 ` [Bug c/105863] RFE: C23 #embed hpa at zytor dot com
2023-06-22 15:16 ` mpolacek at gcc dot gnu.org
2023-06-22 20:42 ` joseph at codesourcery dot com
2024-05-15 15:33 ` jakub at gcc dot gnu.org
2024-05-15 16:16 ` hpa at zytor dot com
2024-05-16 20:41 ` jsm28 at gcc dot gnu.org [this message]
2024-05-17 12:08 ` jakub at gcc dot gnu.org
2024-05-20 20:35 ` jsm28 at gcc dot gnu.org
2024-06-11 15:01 ` jakub at gcc dot gnu.org
2024-06-13 14:45 ` jakub at gcc dot gnu.org
2024-06-14  8:19 ` jakub at gcc dot gnu.org
2024-06-14 19:35 ` jakub at gcc dot gnu.org

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=bug-105863-4-wpcX2wX84E@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).