public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: GCC Development <gcc@gcc.gnu.org>
Cc: Richard Guenther <rguenther@suse.de>,
	Jan Hubicka <hubicka@ucw.cz>,
	gcc-patches@gcc.gnu.org,
		Michael Zolotukhin <michael.v.zolotukhin@gmail.com>,
	Jakub Jelinek <jakub@redhat.com>,
		"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: GCC 4.7.0 Status Report (2011-10-27), Stage 1 will end Nov 7th
Date: Thu, 27 Oct 2011 14:47:00 -0000	[thread overview]
Message-ID: <CAFULd4Y3Vs1Bf8q=XQNooyuy_quv9DHUFOwa=pNn=9QLHm9hUw@mail.gmail.com> (raw)

Hello!

> The GCC trunk is still in stage1.  Stage1 will last until
> Nov 7th (including, use your timezone to your advantage) after
> which we will have been in stage1 for nearth 8 months.
> In stage3 the trunk will be open for general bugfixing, no
> new features will be accepted.

There is a patch that implements usage of vector instructions in
memmov/memset expanding [1]. The patch was not reviewed for quite some
time, but IIRC, we said that patches that were submitted before Stage
1 closes are still eligible for later stages (after a review of
course).

I think that this feature certainly improves gcc (also taking into
account recent glibc changes in this area), and IMO implements an
important feature for recent processors. I would like to motivate
middle-end and target maintainers to consider the patch for a review
before stage 1 closes, and ultimately ask Release Managers to decide
how to proceed with this patch.

[1] http://gcc.gnu.org/ml/gcc-patches/2011-10/msg02392.html

Thanks,
Uros.

             reply	other threads:[~2011-10-27 13:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 14:47 Uros Bizjak [this message]
2011-11-15 15:28 ` Michael Zolotukhin
  -- strict thread matches above, loose matches on Subject: below --
2011-10-27 12:58 Richard Guenther

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='CAFULd4Y3Vs1Bf8q=XQNooyuy_quv9DHUFOwa=pNn=9QLHm9hUw@mail.gmail.com' \
    --to=ubizjak@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=michael.v.zolotukhin@gmail.com \
    --cc=rguenther@suse.de \
    /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).