public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/64026] Many FAIL: ... scan-tree-dump-times vect "Vectorizing an unaligned access" 0 with -fpic Date: Sat, 22 Nov 2014 14:28:00 -0000 [thread overview] Message-ID: <bug-64026-4-F3eTYlNWES@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64026-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64026 --- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to Uroš Bizjak from comment #1) > HJ, is it possible to run a regression hunt between these two revisions? Is this FAIL: gcc.dg/vect/vect-simd-clone-6.c (internal compiler error) FAIL: gcc.dg/vect/vect-simd-clone-6.c (test for excess errors) FAIL: gcc.dg/vect/vect-simd-clone-6.c -flto -ffat-lto-objects (internal compiler error) FAIL: gcc.dg/vect/vect-simd-clone-6.c -flto -ffat-lto-objects (test for excess e rrors) new? >From gcc-bugs-return-468068-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 22 14:36:56 2014 Return-Path: <gcc-bugs-return-468068-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 15352 invoked by alias); 22 Nov 2014 14:36:55 -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 15329 invoked by uid 48); 22 Nov 2014 14:36:52 -0000 From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/64026] Many FAIL: ... scan-tree-dump-times vect "Vectorizing an unaligned access" 0 with -fpic Date: Sat, 22 Nov 2014 14:36: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: X-Bugzilla-Severity: normal X-Bugzilla-Who: ubizjak at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-64026-4-nz8czKCX7H@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64026-4@http.gcc.gnu.org/bugzilla/> References: <bug-64026-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-11/txt/msg02540.txt.bz2 Content-length: 571 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64026 --- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> --- (In reply to H.J. Lu from comment #2) > Is this > > FAIL: gcc.dg/vect/vect-simd-clone-6.c (internal compiler error) > FAIL: gcc.dg/vect/vect-simd-clone-6.c (test for excess errors) > FAIL: gcc.dg/vect/vect-simd-clone-6.c -flto -ffat-lto-objects (internal > compiler > error) > FAIL: gcc.dg/vect/vect-simd-clone-6.c -flto -ffat-lto-objects (test for > excess e > rrors) > > new? I don't know, but I have reported this in a separate PR64024. >From gcc-bugs-return-468069-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 22 14:40:07 2014 Return-Path: <gcc-bugs-return-468069-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 16566 invoked by alias); 22 Nov 2014 14:40:07 -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 16506 invoked by uid 48); 22 Nov 2014 14:40:04 -0000 From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/60770] disappearing clobbers Date: Sat, 22 Nov 2014 14:40: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: 4.9.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: glisse at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: <bug-60770-4-StF7WR55mr@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-60770-4@http.gcc.gnu.org/bugzilla/> References: <bug-60770-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/msg02541.txt.bz2 Content-length: 504 https://gcc.gnu.org/bugzilla/show_bug.cgi?id`770 Marc Glisse <glisse at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #12 from Marc Glisse <glisse at gcc dot gnu.org> --- Clobbers are now properly preserved in this case. We don't warn yet, but that's PR 60517.
next prev parent reply other threads:[~2014-11-22 14:28 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-22 13:34 [Bug tree-optimization/64026] New: " ubizjak at gmail dot com 2014-11-22 13:36 ` [Bug tree-optimization/64026] " ubizjak at gmail dot com 2014-11-22 14:28 ` hjl.tools at gmail dot com [this message] 2014-11-22 17:31 ` hjl.tools at gmail dot com 2014-11-22 17:38 ` [Bug tree-optimization/64026] [5 Rehression] " hjl.tools at gmail dot com 2014-11-24 11:25 ` [Bug tree-optimization/64026] [5 Regression] " rguenth at gcc dot gnu.org 2014-11-24 11:29 ` 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-64026-4-F3eTYlNWES@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).