public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mkgnu at gmx dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/12285] Add sizeof_function functionality Date: Thu, 18 Sep 2003 16:03:00 -0000 [thread overview] Message-ID: <20030918155041.2305.qmail@sources.redhat.com> (raw) In-Reply-To: <20030915054549.12285.mkgnu@gmx.net> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12285 ------- Additional Comments From mkgnu at gmx dot net 2003-09-18 15:50 ------- The use of sizeof_function() would be to calculate during compile the size of a function's text segment. One may want to copy that function during runtime and create multiple copies of it (e.g. create new functions based on a template). I am not sure what needs to happen on the case that a function has multiple entry points. Any C function you compile will result into a text segment. I don't see where the multiple entrypoints are. It may be called from different other functions, but that doesn't matter. I don't think I understand what you mean. Please read the thread.
next prev parent reply other threads:[~2003-09-18 15:50 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-09-15 8:52 [Bug c/12285] New: " mkgnu at gmx dot net 2003-09-18 7:34 ` [Bug middle-end/12285] " pinskia at gcc dot gnu dot org 2003-09-18 16:03 ` mkgnu at gmx dot net [this message] 2003-09-19 6:27 ` wilson at specifixinc dot com 2003-09-19 9:52 ` mkgnu at gmx dot net 2004-01-01 1:04 ` pinskia at gcc dot gnu dot org 2004-01-01 19:16 ` mkgnu at gmx dot net 2004-04-27 19:05 ` pinskia at gcc dot gnu dot 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=20030918155041.2305.qmail@sources.redhat.com \ --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: linkBe 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).