public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/13850] [tree-ssa] Fails to compile ffmpeg on x86: can't find a register in class `GENERAL_REGS' while reloading `asm'
Date: Wed, 04 Feb 2004 02:54:00 -0000	[thread overview]
Message-ID: <20040204025412.11353.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040124223232.13850.bero@arklinux.org>


------- Additional Comments From rth at gcc dot gnu dot org  2004-02-04 02:54 -------
Yes, all of this is quite silly, and should be using <mmintrin.h> instead.

That said, I compute 4 required registers here, so we should have been ok.
The bug appears to be that CSE isn't interested in generating more complex
addressing modes for the memories here.  Not sure why...

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |rth at gcc dot gnu dot org
                   |dot org                     |
             Status|NEW                         |ASSIGNED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13850


  parent reply	other threads:[~2004-02-04  2:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-24 22:32 [Bug inline-asm/13850] New: Fails to compile ffmpeg on x86: can't find a register in class `GENERAL_REGS' while reloading `asm'can't " bero at arklinux dot org
2004-01-24 22:33 ` [Bug inline-asm/13850] " bero at arklinux dot org
2004-01-24 22:41 ` [Bug inline-asm/13850] Fails to compile ffmpeg on x86: can't " pinskia at gcc dot gnu dot org
2004-01-24 22:42 ` bero at arklinux dot org
2004-01-24 22:44 ` pinskia at gcc dot gnu dot org
2004-01-24 22:58 ` bero at arklinux dot org
2004-01-25  1:48 ` [Bug optimization/13850] [tree-ssa] " pinskia at gcc dot gnu dot org
2004-02-04  2:54 ` rth at gcc dot gnu dot org [this message]
2004-02-04  3:21 ` bero at arklinux dot org
2004-02-04  3:46 ` rth at redhat dot com
2004-03-12  5:01 ` pinskia at gcc dot gnu dot org
2004-03-12 23:44 ` mog dot johnny at gmx dot net
2004-06-06 11:54 ` [Bug rtl-optimization/13850] [3.5 Regression] " v dot merkatz at gmx dot net
2004-07-02 19:23 ` [Bug rtl-optimization/13850] " pinskia at gcc dot gnu dot org
2004-07-25 16:00 ` jbernardo at sourcemage dot org
2004-07-25 16:04 ` jbernardo at sourcemage dot org
2004-08-06  7:01 ` pinskia at gcc dot gnu dot 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=20040204025412.11353.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).