public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "froydnj at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/46259] [4.6 Regression] Revision 166102 failed 416.gamess in SPEC CPU 2006
Date: Mon, 01 Nov 2010 18:58:00 -0000	[thread overview]
Message-ID: <20101101185800._JUf-e5xh7hyM2fay2VkWLLXMxYG04jX8MMFj15h3OY@z> (raw)
In-Reply-To: <bug-46259-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46259

--- Comment #8 from Nathan Froyd <froydnj at gcc dot gnu.org> 2010-11-01 18:58:35 UTC ---
Author: froydnj
Date: Mon Nov  1 18:58:30 2010
New Revision: 166139

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=166139
Log:
gcc/
2010-11-01  Nathan Froyd  <froydnj@codesourcery.com>

    PR tree-optimization/46259

    Revert:

    2010-10-30  Nathan Froyd  <froydnj@codesourcery.com>

    * tree-vect-stmts.c (vect_get_vec_def_for_operand): Use
    build_vector_from_val.

gcc/testsuite/
2010-11-01  H.J. Lu  <hongjiu.lu@intel.com>
        Nathan Froyd  <froydnj@codesourcery.com>

    PR tree-optimization/46259
    * gfortran.dg/pr46259.f: New testcase.

Added:
    trunk/gcc/testsuite/gfortran.dg/pr46259.f
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-vect-stmts.c


  parent reply	other threads:[~2010-11-01 18:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 14:37 [Bug tree-optimization/46259] New: " hjl.tools at gmail dot com
2010-11-01 14:37 ` [Bug tree-optimization/46259] " hjl.tools at gmail dot com
2010-11-01 14:41 ` froydnj at codesourcery dot com
2010-11-01 14:48 ` hjl.tools at gmail dot com
2010-11-01 14:49 ` hjl.tools at gmail dot com
2010-11-01 14:50 ` hjl.tools at gmail dot com
2010-11-01 14:57 ` froydnj at codesourcery dot com
2010-11-01 16:21 ` hjl.tools at gmail dot com
2010-11-01 16:33 ` hjl.tools at gmail dot com
2010-11-01 18:58 ` froydnj at gcc dot gnu.org [this message]
2010-11-01 20:04 ` jakub at gcc dot gnu.org

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=20101101185800._JUf-e5xh7hyM2fay2VkWLLXMxYG04jX8MMFj15h3OY@z \
    --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).