From: Jack Howarth <howarth@bromo.med.uc.edu>
To: gcc@gcc.gnu.org
Subject: more graphite merges before gcc 4.5 branch?
Date: Thu, 12 Nov 2009 17:03:00 -0000 [thread overview]
Message-ID: <20091112170336.GA7516@bromo.med.uc.edu> (raw)
Are there any plans for further merges out of the
graphite branch before gcc 4.5 is branched? I was
under the impression that the graphite developers
originally intended to keep trunk more closely
synchronized with the graphite branch during the
gcc 4.5 release cycle and this doesn't seem to have
happened. It would be a shame to see graphite's
performance be suboptimal for another release cycle.
Jack
next reply other threads:[~2009-11-12 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 17:03 Jack Howarth [this message]
2009-11-12 18:23 ` David Edelsohn
2009-11-13 15:11 ` Jack Howarth
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=20091112170336.GA7516@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=gcc@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).