public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Thomas Preud'homme" <thomas.preudhomme@arm.com>
To: "'Jeff Law'" <law@redhat.com>,	"'Andrew Pinski'" <pinskia@gmail.com>
Cc: "Eric Botcazou" <ebotcazou@adacore.com>,
	"GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH 1/2, combine] Try REG_EQUAL for nonzero_bits
Date: Wed, 11 Feb 2015 06:43:00 -0000	[thread overview]
Message-ID: <00f401d045c5$f0853540$d18f9fc0$@arm.com> (raw)
In-Reply-To: <54DAF0CD.9030701@redhat.com>

> From: Jeff Law [mailto:law@redhat.com]
> Sent: Wednesday, February 11, 2015 2:04 PM
> 
> Given the rs6000 is affected, one could do before/after tests natively
> in the gcc farm to ensure that removing that code doesn't change the
> generated code across a bootstrap.

Wouldn't that only tell whether the macro can stay undefined for rs6000?
MD files for rs6000 could have been tighten since then but not others
backend's MD files.

> 
> That's probably how I'd approach gathering some data about whether or
> not the comment/code is still appropriate/needed.

Do people with svn access automatically have access to the GCC farm or
does one needs to request such access?

Best regards,

Thomas




  reply	other threads:[~2015-02-11  6:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10  1:52 Thomas Preud'homme
2015-02-10  1:57 ` Andrew Pinski
2015-02-10  2:19   ` Thomas Preud'homme
2015-02-11  6:04     ` Jeff Law
2015-02-11  6:43       ` Thomas Preud'homme [this message]
2015-02-11  6:48         ` Jeff Law
2015-02-11  6:56           ` Thomas Preud'homme
2015-04-24 10:43             ` Thomas Preud'homme
2015-02-12  8:35       ` Alan Modra
2015-02-13  9:40         ` Thomas Preud'homme
2015-04-24 18:57 ` Jeff Law
2015-04-27 11:03   ` Thomas Preud'homme

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='00f401d045c5$f0853540$d18f9fc0$@arm.com' \
    --to=thomas.preudhomme@arm.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=pinskia@gmail.com \
    /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).