From: Basile STARYNKEVITCH <basile@starynkevitch.net>
To: GCC Mailing List <gcc@gcc.gnu.org>
Subject: checking for debug a plugin on a production compiler?
Date: Wed, 14 Oct 2009 21:28:00 -0000 [thread overview]
Message-ID: <4AD62FA1.9070207@starynkevitch.net> (raw)
Hello All
Is the following scenario possible:
gcc-4.5 is being released at Christmas 2009 [*]. Since it is a
production compiler, it has been compiled without any checking (no
ENABLE_CHECKING, etc...)
a plugin foo.c is compiled as foo.so for that gcc-4.5, but since the
plugin is probably buggy, it is compiled with ENABLE_CHECKING.
This should probably work if ENABLE_CHECKING does not add extra fields
in data structure, but only runs checks without "side-effects" - other
than consume CPU resources (& memory)... In other words, if
ENABLE_CHECKING only enables gcc_assert and similar stuff (that is, only
add code but not "data" inside GCC, if you guess what I am thinking of).
If this is impossible (for instance because ENABLE_CHECKING modifies the
data structure inside GCC), we might consider documenting that.
Regards.
Note [*]: I don't pretend knowing when 4.5 will be released, and its
release date is not the subject of that discussion!
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***
next reply other threads:[~2009-10-14 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 21:28 Basile STARYNKEVITCH [this message]
2009-10-15 22:30 ` Rafael Espindola
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=4AD62FA1.9070207@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=gcc@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).