public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/59163] [4.8/4.9 Regression] program compiled with g++ -O3 segfaults Date: Fri, 29 Nov 2013 19:56:00 -0000 [thread overview] Message-ID: <bug-59163-4-Vtyjk5Lv4G@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59163-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59163 --- Comment #14 from Uroš Bizjak <ubizjak at gmail dot com> --- (In reply to Uroš Bizjak from comment #13) > (In reply to Jakub Jelinek from comment #12) > > Created attachment 31332 [details] > > gcc49-pr59163.patch > > > > So like this? > > Yes, with adjusted comment in ix86_legitimate_combined_insn. > > IIRC, unaligned moves won't be propagated during or after reload, so it > looks to me that the approach is correct. Running the testsuite with your patch applied exposed a minor problem: FAIL: gcc.target/i386/sse-1.c scan-assembler-not movaps movlps/movhps and movlpd/movhpd can also handle unaligned operands (please see ix86_expand_vector_move_misalign). We should simply tag instructions that operate on unaligned operands (attribute type = ssemovu) and check type attribute instead. The proposed approach would mean to change all scheduler and attribute calculation checks from "ssemov" to "ssemov,ssemovu", but this would be a simple mechanical change. >From gcc-bugs-return-436290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 20:06:13 2013 Return-Path: <gcc-bugs-return-436290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 8990 invoked by alias); 29 Nov 2013 20:06:13 -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 8931 invoked by uid 48); 29 Nov 2013 20:06:10 -0000 From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/59333] ICE with long long and -m32 -fsanitize=undefined Date: Fri, 29 Nov 2013 20:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59333-4-Dn10wwkVeU@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59333-4@http.gcc.gnu.org/bugzilla/> References: <bug-59333-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: 2013-11/txt/msg03067.txt.bz2 Content-length: 203 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY333 --- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> --- I think we just shouldn't try to pass values by reference in ubsan_encode_value...
next prev parent reply other threads:[~2013-11-29 19:56 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-17 22:44 [Bug c++/59163] New: " donnyjward at gmail dot com 2013-11-18 10:49 ` [Bug rtl-optimization/59163] " redi at gcc dot gnu.org 2013-11-18 11:41 ` [Bug rtl-optimization/59163] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org 2013-11-21 14:49 ` [Bug tree-optimization/59163] " rguenth at gcc dot gnu.org 2013-11-29 8:16 ` jakub at gcc dot gnu.org 2013-11-29 8:52 ` jakub at gcc dot gnu.org 2013-11-29 9:22 ` [Bug target/59163] " rguenth at gcc dot gnu.org 2013-11-29 10:34 ` jakub at gcc dot gnu.org 2013-11-29 12:57 ` ubizjak at gmail dot com 2013-11-29 13:43 ` ubizjak at gmail dot com 2013-11-29 14:38 ` jakub at gcc dot gnu.org 2013-11-29 16:28 ` ubizjak at gmail dot com 2013-11-29 16:39 ` ubizjak at gmail dot com 2013-11-29 16:57 ` jakub at gcc dot gnu.org 2013-11-29 18:14 ` ubizjak at gmail dot com 2013-11-29 19:56 ` ubizjak at gmail dot com [this message] 2013-11-29 20:28 ` jakub at gcc dot gnu.org 2013-11-29 20:54 ` jakub at gcc dot gnu.org 2013-11-30 7:14 ` jakub at gcc dot gnu.org 2013-11-30 9:59 ` ubizjak at gmail dot com 2013-12-04 11:11 ` jakub at gcc dot gnu.org 2013-12-04 11:12 ` jakub at gcc dot gnu.org 2013-12-04 15:51 ` jakub at gcc dot gnu.org 2013-12-04 15:55 ` jakub at gcc dot gnu.org 2013-12-10 7:50 ` 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=bug-59163-4-Vtyjk5Lv4G@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).