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 tree-optimization/32093] BOOT_CFLAGS="-O2 -g -msse2 -ftree-vectorize" causes dfp tests to fail
Date: Sun, 17 Jun 2007 08:54:00 -0000 [thread overview]
Message-ID: <20070617085353.18577.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32093-6528@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from ubizjak at gmail dot com 2007-06-17 08:53 -------
(In reply to comment #2)
> i'm wondering if this could be related to a problem we're seeing with segfaults
> caused by misaligned movdqa instructions in zlib compiled with
> -ftree-vectorize.
Please open a new bug for this problem.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32093
next prev parent reply other threads:[~2007-06-17 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 9:18 [Bug tree-optimization/32093] New: " pinskia at gcc dot gnu dot org
2007-06-16 12:57 ` [Bug tree-optimization/32093] " hjl at lucon dot org
2007-06-16 23:51 ` dirtyepic at gentoo dot org
2007-06-17 8:54 ` ubizjak at gmail dot com [this message]
2007-07-24 8:51 ` dorit at gcc dot gnu dot org
[not found] <bug-32093-4@http.gcc.gnu.org/bugzilla/>
2021-08-22 3:44 ` pinskia 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=20070617085353.18577.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: link
Be 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).