public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kbowers at lanl dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/12902] Invalid assembly generated when using SSE / xmmintrin.h
Date: Tue, 09 Dec 2003 18:01:00 -0000 [thread overview]
Message-ID: <20031209180113.24015.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031105013127.12902.kbowers@lanl.gov>
------- Additional Comments From kbowers at lanl dot gov 2003-12-09 18:01 -------
Over a month ago, I reported this bug and then went to the effort to learning
gcc's internals in order to submit patches. However, the bug is still listed as
new and there has been no response for roughly a month.
Will these patches (or some other fix) be incorporated into a future release of gcc?
The reason I ask is it is unreasonable for me to require users to both patch and
build their own compiler to install some scientific codes of mine on large
clusters. I would like to see this bug resolved quickly so I can continue to
recommend gcc as the preferred compiler. Given I've already submitted patches,
this should be easy to address.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12902
next prev parent reply other threads:[~2003-12-09 18:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 1:31 [Bug c++/12902] New: " kbowers at lanl dot gov
2003-11-05 4:08 ` [Bug c++/12902] " pinskia at gcc dot gnu dot org
2003-11-05 5:51 ` kbowers at lanl dot gov
2003-11-06 18:53 ` kbowers at lanl dot gov
2003-11-07 1:02 ` kbowers at lanl dot gov
2003-11-07 10:42 ` kbowers at lanl dot gov
2003-12-09 18:01 ` kbowers at lanl dot gov [this message]
2003-12-09 20:14 ` [Bug target/12902] " dhazeghi at yahoo dot com
2003-12-09 20:17 ` dhazeghi at yahoo dot com
2003-12-11 16:07 ` bangerth at dealii dot org
2004-12-13 20:54 ` bangerth at dealii dot org
2004-12-14 10:54 ` uros at kss-loka dot si
2005-01-05 9:43 ` [Bug target/12902] [4.0 Regression] " uros at kss-loka dot si
2005-01-05 12:14 ` rth at gcc dot gnu dot org
2005-01-05 19:14 ` cvs-commit at gcc dot gnu dot org
2005-01-05 20:04 ` rth at gcc dot gnu dot org
2005-01-06 8:25 ` uros at kss-loka dot si
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=20031209180113.24015.qmail@sources.redhat.com \
--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).