public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/67830] [6 Regression] wrong code at -O1 and above on x86_64-linux-gnu
Date: Fri, 23 Oct 2015 19:17:00 -0000	[thread overview]
Message-ID: <bug-67830-4-uby5ufo6Lt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67830-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67830

--- Comment #6 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Author: law
Date: Fri Oct 23 19:16:53 2015
New Revision: 229267

URL: https://gcc.gnu.org/viewcvs?rev=229267&root=gcc&view=rev
Log:
[RFA] Fix pr67830, another type narrowing problem

        PR tree-optimization/67830
        * match.pd ((bit_and (plus/minus (convert @0) (convert @1)) mask)):
        Explicitly verify the mask has no bits outside the type of
        the innermost operands.

        PR tree-optimization/67830
        * gcc.dg/pr67830.c: New test.

Added:
    trunk/gcc/testsuite/gcc.dg/pr67830.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/match.pd
    trunk/gcc/testsuite/ChangeLog


      parent reply	other threads:[~2015-10-23 19:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-03  5:38 [Bug rtl-optimization/67830] New: " su at cs dot ucdavis.edu
2015-10-05  8:32 ` [Bug tree-optimization/67830] [6 Regression] " rguenth at gcc dot gnu.org
2015-10-05  8:43 ` rguenth at gcc dot gnu.org
2015-10-05 10:11 ` mpolacek at gcc dot gnu.org
2015-10-05 18:54 ` law at redhat dot com
2015-10-23 19:17 ` law at redhat dot com
2015-10-23 19:17 ` law at gcc dot gnu.org [this message]

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-67830-4-uby5ufo6Lt@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: 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).