public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: gcc-patches@gcc.gnu.org
Subject: Ping^2 Re: Create common hooks structure shared between driver and cc1
Date: Fri, 10 Jun 2011 14:56:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1106101437250.1616@digraph.polyomino.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1106060902390.24559@digraph.polyomino.org.uk>

Ping^2.  This patch 
<http://gcc.gnu.org/ml/gcc-patches/2011-05/msg01907.html>, and the 
followup <http://gcc.gnu.org/ml/gcc-patches/2011-05/msg02172.html>, are 
pending review after two weeks.  Together these patches create and 
populate a common structure of target hooks shared between the driver and 
cc1.

I also described in those threads (in particular in 
<http://gcc.gnu.org/ml/gcc-patches/2011-05/msg01779.html>) further 
cleanups possible after these patches for anyone interested in converting 
more common target macros to hooks or in moving source files around to 
reflect a more modular structure for common code.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2011-06-10 14:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25  0:25 Joseph S. Myers
2011-05-25 19:54 ` Joseph S. Myers
2011-05-25 21:40   ` Tom Tromey
2011-05-25 22:37     ` Joseph S. Myers
2011-05-25 23:56   ` Mike Stump
2011-05-26  0:16     ` Joseph S. Myers
2011-05-26  0:19       ` Mike Stump
2011-06-06  9:03   ` Ping " Joseph S. Myers
2011-06-10 14:56     ` Joseph S. Myers [this message]
2011-06-14 17:29   ` Ian Lance Taylor

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=Pine.LNX.4.64.1106101437250.1616@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=gcc-patches@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).