public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sergstesh at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/29818] code with SSE segfaults with gcc-3.4.6, runs fine with gcc-4.1.1 Date: Fri, 17 Nov 2006 01:27:00 -0000 [thread overview] Message-ID: <20061117012730.7549.qmail@sourceware.org> (raw) In-Reply-To: <bug-29818-13529@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from sergstesh at yahoo dot com 2006-11-17 01:27 ------- Please see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29874 - another proof that gcc-3.4.6 generates better SSE code than gcc-4.1.1, and the proof uses only widely available and well known GPL'ed code. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29818
next prev parent reply other threads:[~2006-11-17 1:27 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-13 16:36 [Bug c/29818] New: " sergstesh at yahoo dot com 2006-11-13 16:40 ` [Bug c/29818] " sergstesh at yahoo dot com 2006-11-13 18:35 ` [Bug target/29818] " pinskia at gcc dot gnu dot org 2006-11-14 0:53 ` pinskia at gcc dot gnu dot org 2006-11-14 1:04 ` sergstesh at yahoo dot com 2006-11-14 1:17 ` pcarlini at suse dot de 2006-11-14 1:37 ` sergstesh at yahoo dot com 2006-11-14 2:29 ` bangerth at dealii dot org 2006-11-14 2:54 ` sergstesh at yahoo dot com 2006-11-17 1:27 ` sergstesh at yahoo dot com [this message] 2006-11-17 1:46 ` pinskia at gcc dot gnu dot org 2006-11-17 2:03 ` sergstesh at yahoo dot com 2006-11-17 2:09 ` bangerth at dealii dot org 2006-11-17 2:12 ` bangerth at dealii dot org 2006-11-17 2:23 ` sergstesh at yahoo dot com 2006-11-19 1:27 ` pinskia at gcc dot gnu dot org 2006-11-19 1:59 ` sergstesh at yahoo dot com 2006-11-19 2:06 ` pinskia at gcc dot gnu dot org 2006-11-19 2:20 ` sergstesh at yahoo 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=20061117012730.7549.qmail@sourceware.org \ --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).