public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47269] DSYMUTIL_SPEC doesn't handle -gtoggle
Date: Sun, 06 Feb 2011 02:15:00 -0000 [thread overview]
Message-ID: <bug-47269-4-Rim5d8jXZ7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47269-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47269
--- Comment #4 from Jack Howarth <howarth at nitro dot med.uc.edu> 2011-02-06 02:15:08 UTC ---
Mike,
I thought it was pretty clear in the man page...
-gtoggle
Turn off generation of debug info, if leaving out this option would
have generated it, or turn it on at level 2 otherwise. The
position of this argument in the command line does not matter, it
takes effect after all other options are processed, and it does so
only once, no matter how many times it is given. This is mainly
intended to be used with -fcompare-debug.
It inverts whatever the final status of debug code generation was. I think this
is why
you see it handled in toplev.c...
if (flag_gtoggle)
{
if (debug_info_level == DINFO_LEVEL_NONE)
{
debug_info_level = DINFO_LEVEL_NORMAL;
if (write_symbols == NO_DEBUG)
write_symbols = PREFERRED_DEBUGGING_TYPE;
}
else
debug_info_level = DINFO_LEVEL_NONE;
}
rather than in opts.c.
prev parent reply other threads:[~2011-02-06 2:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 15:45 [Bug target/47269] New: " howarth at nitro dot med.uc.edu
2011-01-13 5:46 ` [Bug target/47269] " howarth at nitro dot med.uc.edu
2011-02-06 1:10 ` mikestump at comcast dot net
2011-02-06 1:32 ` mikestump at comcast dot net
2011-02-06 2:15 ` howarth at nitro dot med.uc.edu [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=bug-47269-4-Rim5d8jXZ7@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).