public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/53072] automatically set Init() only if option was not set in some other way
Date: Tue, 24 Apr 2012 13:59:00 -0000	[thread overview]
Message-ID: <bug-53072-4-ePPlU6lzWq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53072-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53072

--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-04-24 13:59:10 UTC ---
On Sun, 22 Apr 2012, manu at gcc dot gnu.org wrote:

> The infrastructure to detect whether options have been set explicitly seems to
> be there, but it is not clear how to use it to fix the above problem.

My notion is that the _set information should move from being a boolean to 
recording the "distance" of the option that set some field from that field 
(it might be set by an option that directly corresponds to the field, or 
by one indirectly implying it, or a default if no relevant option is given 
at all).  Distance is in the sense of appendix 1 of 
<http://gcc.gnu.org/ml/gcc/2010-01/msg00063.html>.

This is explicitly not a detailed design; anyone implementing it would 
need to flesh out the details.


  reply	other threads:[~2012-04-24 13:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-22 16:51 [Bug c/53072] New: " manu at gcc dot gnu.org
2012-04-24 13:59 ` joseph at codesourcery dot com [this message]
2012-04-24 14:11 ` [Bug c/53072] " manu at gcc dot gnu.org
2012-04-24 14:44 ` joseph at codesourcery dot com
2012-04-24 14:51 ` manu at gcc dot gnu.org
2012-04-24 15:09 ` joseph at codesourcery dot com
2012-04-28  0:17 ` manu at gcc dot gnu.org
2012-05-13 22:34 ` manu 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-53072-4-ePPlU6lzWq@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).