public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rainer@emrich-ebersheim.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65561] avx512fintrin.h:5344:1: internal compiler error: in curr_insn_transform, at lra-constraints.c:3494 Date: Thu, 26 Mar 2015 15:40:00 -0000 [thread overview] Message-ID: <bug-65561-4-nZadZXcjPo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65561-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65561 --- Comment #4 from Rainer Emrich <rainer@emrich-ebersheim.de> --- (In reply to Uroš Bizjak from comment #3) > Rainer, the failure doesn't trigger for me on crosscompiler from > x86_64-linux-gnu. Can you please check if the attached patch fixes the > failure for you? I will try that in the evening, a few hours from now. >From gcc-bugs-return-481838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Mar 26 14:44:39 2015 Return-Path: <gcc-bugs-return-481838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 52910 invoked by alias); 26 Mar 2015 14:44:39 -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 52833 invoked by uid 48); 26 Mar 2015 14:44:30 -0000 From: "jgreenhalgh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/65551] [5 Regression] FAIL: 26_numerics/complex/50880.cc execution test Date: Thu, 26 Mar 2015 15:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jgreenhalgh at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: thopre01 at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-65551-4-z047XkNQjL@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-65551-4@http.gcc.gnu.org/bugzilla/> References: <bug-65551-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: 2015-03/txt/msg02982.txt.bz2 Content-length: 180 https://gcc.gnu.org/bugzilla/show_bug.cgi?ide551 --- Comment #5 from James Greenhalgh <jgreenhalgh at gcc dot gnu.org> --- I'll kick off the same for arm-none-linux-gnueabihf.
next prev parent reply other threads:[~2015-03-26 14:38 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-25 18:22 [Bug target/65561] New: " rainer@emrich-ebersheim.de 2015-03-25 19:08 ` [Bug target/65561] " ktietz at gcc dot gnu.org 2015-03-26 15:09 ` ubizjak at gmail dot com 2015-03-26 15:40 ` rainer@emrich-ebersheim.de [this message] 2015-03-26 18:58 ` rainer@emrich-ebersheim.de 2015-03-26 21:35 ` uros at gcc dot gnu.org 2015-03-26 21:51 ` ubizjak at gmail dot com 2015-03-27 0:04 ` uros at gcc dot gnu.org 2015-03-27 0:15 ` ubizjak at gmail dot com
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-65561-4-nZadZXcjPo@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: linkBe 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).