public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dirtyepic at gentoo dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/48524] New: spec language does not cover switches with separated form Date: Sat, 09 Apr 2011 02:35:00 -0000 [thread overview] Message-ID: <bug-48524-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48524 Summary: spec language does not cover switches with separated form Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: driver AssignedTo: unassigned@gcc.gnu.org ReportedBy: dirtyepic@gentoo.org Up until 4.6.0, we could write a simple spec rule for an arbitrary preprocessor definition like: %{!U_FORTIFY_SOURCE:-D_FORTIFY_SOURCE=2} -D and -U flags have both joined and separate forms and the above rule worked as long as the joined form was used. This was good enough for the most part, since the separate form is rare enough that I didn't even know it existed until now. As of 4.6.0, as outlined in PR47236, these flags are now regenerated in their canonical, separate, form for specs processing with the benefit that specs no longer have to handle the non-canonical cases. The problem we have though, is that there doesn't actually seem to be any way to write a spec rule for a switch substitution using the separated form, or at least any that I've found. The above rule no longer matches, and whitespace and wildcard characters don't seem to be allowed in switch names. I'd like to request that the spec language be extended to provide a way to match separate-form switches, which would restore the functionality we need. This is both an enhancement request and, in my point of view, a regression, since the loss of the ability to write specs matching preprocessor symbols has broken several of our projects in ways that would be very difficult to fix otherwise.
next reply other threads:[~2011-04-09 2:35 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-09 2:35 dirtyepic at gentoo dot org [this message] 2011-04-09 11:28 ` [Bug driver/48524] " joseph at codesourcery dot com 2011-04-09 18:51 ` dirtyepic at gentoo dot org 2011-04-10 0:27 ` joseph at codesourcery dot com 2011-04-12 2:22 ` vapier at gentoo dot org 2011-04-13 3:49 ` dirtyepic at gentoo dot org 2011-12-17 20:33 ` zorry at gentoo dot org 2011-12-17 21:22 ` zorry at gentoo dot org 2011-12-18 20:46 ` zorry at gentoo dot org 2012-02-08 21:38 ` jsm28 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-48524-4@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).