public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/67304] Allow front-ends to share command-line options with different behaviours Date: Fri, 21 Aug 2015 12:40:00 -0000 [thread overview] Message-ID: <bug-67304-4-VJJsqVhd39@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67304-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67304 Manuel López-Ibáñez <manu at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manu at gcc dot gnu.org --- Comment #2 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Iain Buclaw from comment #0) > However I am not too familiar with the awk files used in the process, so I'm > not sure how much of an undertaking this will be. >From my own experience, being familiar with awk is not really needed. You just need to figure out what C++ code you want to generate (options.c, options.h) and how it will interact with the rest of GCC. I will suggest that you actually prototype your changes directly hacking options.c and options.h, then you modify the awk scripts to generate that code. Modifying the scripts is not that complex, just printing the right things at the right place (probably our awk scripts can be very much cleaned up and optimized but it hasn't been an issue so far). >From gcc-bugs-return-495348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Aug 21 13:12:20 2015 Return-Path: <gcc-bugs-return-495348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 24194 invoked by alias); 21 Aug 2015 13:12:19 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 24165 invoked by uid 48); 21 Aug 2015 13:12:16 -0000 From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/67306] Patterns ICEs when moved using "simplify and match" Date: Fri, 21 Aug 2015 13:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed Message-ID: <bug-67306-4-nIOUaev8i4@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-67306-4@http.gcc.gnu.org/bugzilla/> References: <bug-67306-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-08/txt/msg01490.txt.bz2 Content-length: 579 https://gcc.gnu.org/bugzilla/show_bug.cgi?idg306 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2015-08-21 Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Ah, indeed. Mine.
next prev parent reply other threads:[~2015-08-21 12:40 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-21 9:12 [Bug other/67304] New: " ibuclaw at gdcproject dot org 2015-08-21 11:13 ` [Bug other/67304] " joseph at codesourcery dot com 2015-08-21 12:40 ` manu at gcc dot gnu.org [this message] 2015-08-21 14:18 ` ibuclaw at gdcproject dot 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-67304-4-VJJsqVhd39@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).