public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/47236] Spaces introduced in option processing Date: Mon, 10 Jan 2011 00:54:00 -0000 [thread overview] Message-ID: <bug-47236-4-PhPogNWFNj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47236-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47236 Joseph S. Myers <jsm28 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |jsm28 at gcc dot gnu.org Resolution| |INVALID --- Comment #1 from Joseph S. Myers <jsm28 at gcc dot gnu.org> 2011-01-10 00:32:29 UTC --- This has nothing to do with the specs language. Rather, the canonical form of an option accepting both joined and separate arguments is the form with a separate argument, all option processing in both the driver and the core compilers now uses common logic to process options into logical cl_decoded_option structures, and all subsequent processing now uses those structures - and if it needs to regenerate an option for specs processing, uses the canonical form of the option (meaning specs no longer need to handle noncanonical options if they are noncanonical in a way indicated in the .opt files, e.g. through being aliases or through using joined arguments where separate arguments are also accepted). -D options certainly appear to be passed in canonical (separate) form to subprocesses (e.g. by gcc -E) to me. If an option accepts a separate argument and it is passed down to subprocesses by specs, those subprocesses must accept the form with the separate argument.
prev parent reply other threads:[~2011-01-10 0:32 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-09 17:11 [Bug driver/47236] New: " bigotp at acm dot org 2011-01-10 0:54 ` jsm28 at gcc dot gnu.org [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-47236-4-PhPogNWFNj@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: 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).