public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/46805] ICE: SIGSEGV in optab_for_tree_code (optabs.c:407) with -O -fno-tree-scev-cprop -ftree-vectorize Date: Tue, 07 Dec 2010 19:29:00 -0000 [thread overview] Message-ID: <bug-46805-4-EW07sB570G@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46805-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46805 --- Comment #3 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> 2010-12-07 19:28:49 UTC --- Author: ian Date: Tue Dec 7 19:28:44 2010 New Revision: 167563 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=167563 Log: PR tree-optimization/46805 PR tree-optimization/46833 * go-lang.c (go_langhook_type_for_mode): Handle vector modes. Modified: trunk/gcc/go/ChangeLog trunk/gcc/go/go-lang.c
next prev parent reply other threads:[~2010-12-07 19:29 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-05 0:14 [Bug tree-optimization/46805] New: " zsojka at seznam dot cz 2010-12-05 11:07 ` [Bug tree-optimization/46805] " rguenth at gcc dot gnu.org 2010-12-05 11:19 ` zsojka at seznam dot cz 2010-12-07 19:29 ` ian at gcc dot gnu.org [this message] 2010-12-07 19:32 ` ian at airs 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-46805-4-EW07sB570G@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).