public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63965] [5 Regression] ICE: in extract_constrain_insn, at recog.c:2230 on ppc64
Date: Mon, 24 Nov 2014 16:50:00 -0000	[thread overview]
Message-ID: <bug-63965-4-ttq9iRgDqY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63965-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Pat Haugen <pthaugen at gcc dot gnu.org> ---
(In reply to Michael Meissner from comment #6)
> Author: meissner
> Date: Fri Nov 21 18:03:09 2014
> New Revision: 217940
> 
> URL: https://gcc.gnu.org/viewcvs?rev=217940&root=gcc&view=rev
> Log:
> 2014-11-21  Michael Meissner  <meissner@linux.vnet.ibm.com>
> 
> 	PR target/63965
> 	* config/rs6000/rs6000.c (rs6000_setup_reg_addr_masks): Do not set
> 	Altivec & -16 mask if the type is not valid for Altivec registers.
> 	(rs6000_secondary_reload_memory): Add support for ((reg + const) +
> 	reg) that occurs during push_reload processing.
> 
> 	* config/rs6000/altivec.md (altivec_mov<mode>): Add instruction
> 	alternative for moving constant vectors which are easy altivec
> 	constants to GPRs.  Set the length attribute each of the
> 	alternatives.
> 
> 
> Modified:
>     trunk/gcc/ChangeLog
>     trunk/gcc/config/rs6000/rs6000-cpus.def
>     trunk/gcc/config/rs6000/rs6000.c

Looks like the changes checked in do not match the ChangeLog comments, nor the
proposed patch from comment #4.  Revision 217940 also introduced a trunk build
problem when configuring with --with-cpu=power8.
>From gcc-bugs-return-468389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 24 16:51:29 2014
Return-Path: <gcc-bugs-return-468389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4833 invoked by alias); 24 Nov 2014 16:51:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 4771 invoked by uid 48); 24 Nov 2014 16:51:25 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61831] [4.9/ 5 Regression] runtime error: pointer being freed was not allocated
Date: Mon, 24 Nov 2014 16:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cf_known_to_fail
Message-ID: <bug-61831-4-F06zQcpc52@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg02861.txt.bz2
Content-length: 344

https://gcc.gnu.org/bugzilla/show_bug.cgi?ida831

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P4
      Known to fail|4.10.0                      |5.0


  parent reply	other threads:[~2014-11-24 16:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 14:28 [Bug target/63965] New: " trippels at gcc dot gnu.org
2014-11-19 14:46 ` [Bug target/63965] " rguenth at gcc dot gnu.org
2014-11-19 19:55 ` dje at gcc dot gnu.org
2014-11-19 20:04 ` meissner at gcc dot gnu.org
2014-11-19 20:54 ` pthaugen at gcc dot gnu.org
2014-11-20 21:51 ` meissner at gcc dot gnu.org
2014-11-20 21:59 ` meissner at gcc dot gnu.org
2014-11-21 18:11 ` meissner at gcc dot gnu.org
2014-11-21 18:18 ` pthaugen at gcc dot gnu.org
2014-11-24 12:48 ` trippels at gcc dot gnu.org
2014-11-24 16:50 ` pthaugen at gcc dot gnu.org [this message]
2014-11-24 18:59 ` meissner at gcc dot gnu.org
2014-11-24 19:28 ` meissner at gcc dot gnu.org
2014-11-25  7:26 ` trippels 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=bug-63965-4-ttq9iRgDqY@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).