public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jh@suse.cz, kelleycook@comcast.net, nobody@gcc.gnu.org Subject: Re: target/9068: [3.4 regression] [x86] comisd & comiss constraints are incorrect Date: Sat, 11 Jan 2003 00:32:00 -0000 [thread overview] Message-ID: <20030111003211.744.qmail@sources.redhat.com> (raw) Old Synopsis: [x86] comisd & comiss intel-syntax constraints are incorrect New Synopsis: [3.4 regression] [x86] comisd & comiss constraints are incorrect State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Fri Jan 10 16:32:10 2003 State-Changed-Why: Confirmed. This also happens on x86-linux, and has nothing to do with intel asm syntax, since I can reproduce it with this smaller testcase ---------------------------------- int foo(int count, double sum) { return (sum/count > 0.0000001); } -------------------------------- and the following (shorter) command line: tmp/g> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -msse2 x.c x.c: In function `int foo(int, double)': x.c:3: internal compiler error: in get_attr_length_immediate, at insn-attrtab.c :22751 Please submit a full bug report, This is a regression w.r.t. 3.3, where things worked, although probably more by chance. Jan, you are the author of the hunk of code that the patch in this report touches. Can you comment on its validity? Thinking more about it, the original report probably was about this code (which indeed fails only with intel asm syntax): ----------------------------- int foo(double sum) { return (sum > 0.0000001); } ------------------------------- tmp/g> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -msse2 -Wall -march=pentium4 -ffast-math -mfpmath=sse -masm=intel x.c x.c: In function `int foo(double)': x.c:3: internal compiler error: output_operand: operand number missing after %-letter Please submit a full bug report, So it seems as if these were two reports in one. The latter example, however, never worked as long as SSE support is present, which is not surprising since the code the patch in this report touches is unchanged since the first SSE patch to i386.c W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9068
next reply other threads:[~2003-01-11 0:32 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-11 0:32 bangerth [this message] 2003-01-11 10:06 Jan Hubicka 2003-03-21 21:09 hubicka
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=20030111003211.744.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=jh@suse.cz \ --cc=kelleycook@comcast.net \ --cc=nobody@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).