public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: middle-end/5345: ICE when using the "+m" constraint with built-in assembly Date: Mon, 14 Jan 2002 06:16:00 -0000 [thread overview] Message-ID: <20020114141603.1184.qmail@sources.redhat.com> (raw) The following reply was made to PR middle-end/5345; it has been noted by GNATS. From: Craig Rodrigues <rodrigc@mediaone.net> To: Andrew Zabolotny <zap@cobra.ru> Cc: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>, "gcc-prs@gcc.gnu.org" <gcc-prs@gcc.gnu.org>, "rodrigc@gcc.gnu.org" <rodrigc@gcc.gnu.org>, gcc-gnats@gcc.gnu.org Subject: Re: middle-end/5345: ICE when using the "+m" constraint with built-in assembly Date: Mon, 14 Jan 2002 09:15:30 -0500 On Mon, Jan 14, 2002 at 12:31:36PM +0300, Andrew Zabolotny wrote: > On 12 Jan 2002 19:16:26 -0000, rodrigc@gcc.gnu.org wrote: > > clobber > > gcc-ice.cpp:44: confused by earlier errors, bailing out > Hmm... it looks like the problem has been at least partially fixed. Can you > please try to remove the "st" constraint, e.g. the last three lines of the asm > directive will look like this: > > "fmulp %%st(1)\n" // a > : "=&t" (ret), "+m" (x) : "m" (0.5F), "m" (1.5F) > : "eax", "st(1)", "st(2)", "st(3)", "st(4)", "st(5)", "st(6)", "st(7)" > ); Changing the line as you mentioned works with gcc 3.0.3 and gcc 3.1. > Is it reasonable for me to rise this question on gcc mailing list? Where else I > can get an expert advice on built-in gcc assembly? Sure, you can ask on the gcc mailing list. The other mailing list which would be good would be the binutils mailing list: http://sources.redhat.com/binutils/
next reply other threads:[~2002-01-14 14:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-14 6:16 Craig Rodrigues [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-04 4:32 rth 2002-01-14 6:16 Craig Rodrigues 2002-01-12 11:16 rodrigc 2002-01-10 2:06 zap
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=20020114141603.1184.qmail@sources.redhat.com \ --to=rodrigc@mediaone.net \ --cc=gcc-prs@gcc.gnu.org \ --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).