From: Robert Dubner <rdubner@symas.com>
To: <gcc@gcc.gnu.org>
Cc: "'Bob Dubner'" <rdubner@dubner.com>
Subject: Code generation: How to define file-scope static variables?
Date: Mon, 28 Nov 2022 15:28:30 -0600 (CST) [thread overview]
Message-ID: <047c01d90370$5c3ecba0$14bc62e0$@symas.com> (raw)
In-Reply-To:
I am part of a team working on a COBOL front end for GCC.
By reverse engineering other front ends, I learned, some months ago, how
to create a function_decl GENERIC node that is the root of a GENERIC tree
describing an entire function.
By calling the routine cgraph_node::finalize_function() with that
function_decl, the assembly language for that function is created, and all
is well.
But now I need to be able to create the equivalent of a file-scope static
variable in C.
This C program file:
//////////////////
static int dubner_at_work = 123454321;
int main(int argc, char **argv)
{
}
//////////////////
produces, in part, this assembly language:
###############
.file "ccc.c"
.text
.data
.align 4
.type dubner_at_work, @object
.size dubner_at_work, 4
dubner_at_work:
.long 123454321
.text
.globl main
.type main, @function
[...]
###############
In my own GENERIC generation code, I believe that I am creating a proper
translation_unit_decl that contains the block and the vars nodes for
specifying "dubner_at_work".
But I have been unable, after several days of looking, to figure out the
equivalent of "cgraph_node::finalize_function" for a
translation_unit_decl. The resulting assembly language doesn't have a
definition for "dubner_at_work".
Can anybody describe how I can tell the downstream processing that I need
the translation_unit_decl to actually define storage?
Thanks very much,
Bob Dubner.
next reply other threads:[~2022-11-28 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 21:28 Robert Dubner [this message]
2022-11-28 23:01 ` David Malcolm
2022-11-29 2:54 ` Robert Dubner
2022-11-30 17:10 ` Robert Dubner
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='047c01d90370$5c3ecba0$14bc62e0$@symas.com' \
--to=rdubner@symas.com \
--cc=gcc@gcc.gnu.org \
--cc=rdubner@dubner.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).