public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drab at kepler dot fjfi dot cvut dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/36064]  New: could not split insn with -O1 -march=nocona -m32
Date: Sun, 27 Apr 2008 18:55:00 -0000	[thread overview]
Message-ID: <bug-36064-8902@http.gcc.gnu.org/bugzilla/> (raw)

When the attached example is compiled by the
   gcc version 4.4.0 20080426 (experimental) (GCC)
using
------------
   gcc -O1 -march=nocona -m32 -c vorbisfile.c.c -o vorbisfile.o
------------
it produces the following error:

----------------
vorbisfile.c: In function 'ov_time_seek_page':
vorbisfile.c:1622: error: could not split insn
(insn 108 66 156 vorbisfile.c:1620 (parallel [
            (set (reg:DF 8 st)
                (float:DF (mem/c:DI (plus:SI (reg/f:SI 6 bp)
                            (const_int -40 [0xffffffffffffffd8])) [0
pcm_total+0 S8 A8])))
            (clobber (scratch:V4SI))
            (clobber (scratch:V4SI))
            (clobber (mem/c:DI (plus:SI (reg/f:SI 6 bp)
                        (const_int -24 [0xffffffffffffffe8])) [0 S8 A8]))
        ]) 235 {floatdidf2_i387_with_xmm} (nil))
vorbisfile.c:1622: internal compiler error: in final_scan_insn, at final.c:2597
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
----------------

The same error is produced with -march=core2, -march=prescott or
-march=pentium4. This error is not present when -m64 is used instead of -m32,
or when any of the AMD architectures are used, like -march=athlon64 and so on.


-- 
           Summary: could not split insn with -O1 -march=nocona -m32
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: drab at kepler dot fjfi dot cvut dot cz
 GCC build triplet: x86_64-pc-linux-gnu
  GCC host triplet: x86_64-pc-linux-gnu
GCC target triplet: x86_64-pc-linux-gnu


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


             reply	other threads:[~2008-04-27 18:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27 18:55 drab at kepler dot fjfi dot cvut dot cz [this message]
2008-04-27 18:56 ` [Bug rtl-optimization/36064] " drab at kepler dot fjfi dot cvut dot cz
2008-04-28  5:35 ` [Bug target/36064] " ubizjak at gmail dot com
2008-04-28  7:53 ` uros at gcc dot gnu dot org
2008-04-28  8:02 ` ubizjak at gmail dot com

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=bug-36064-8902@http.gcc.gnu.org/bugzilla/ \
    --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).