public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "master_up at post dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/27432] New: -fschedule-insns -O2 -march=athlon cause compilation error
Date: Thu, 04 May 2006 17:26:00 -0000 [thread overview]
Message-ID: <bug-27432-12628@http.gcc.gnu.org/bugzilla/> (raw)
Use -march=athlon-xp -O2 -fschedule-insns
or -march=athlon -O2 -fschedule-insns
gcc version where REPRODUCED:
gcc-3.4-20060307
gcc (GCC) 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)
-------
NOT REPRODUCED by
gcc-3.3.6
There is one more bug looking much similar but amd64 arch... is better add it
here or create new bug???
gcc ERROR------:
gcc: warning: -pipe ignored because -save-temps specified
via_mode.c: In function `ViaMonitorRangesCombine':
via_mode.c:1366: error: unable to find a register to spill in class `AD_REGS'
via_mode.c:1366: error: this is the insn:
(insn:HI 6 27 4 0 (set (reg/v:SI 62 [ twocount ])
(mem/f:SI (plus:SI (reg/f:SI 16 argp)
(const_int 4 [0x4])) [11 twocount+0 S4 A32])) 37
{*movsi_1_nointernunit} (nil)
(expr_list:REG_EQUIV (mem/f:SI (plus:SI (reg/f:SI 16 argp)
(const_int 4 [0x4])) [11 twocount+0 S4 A32])
(nil)))
via_mode.c:1366: confused by earlier errors, bailing out
---COMMAND LINE
gcc -DHAVE_CONFIG_H -I. -I. -I.. -DXFree86Server -DIN_MODULE -DXFree86Module \
-DXFree86LOADER -I/usr/include/xorg -I/usr/include/drm -I/usr/include/X11/dri \
-march=athlon-xp -O2 -pipe -fomit-frame-pointer -Wall -fschedule-insns -MT \
via_mode.lo -MD -MP -MF .deps/via_mode.Tpo -c via_mode.c -fPIC -DPIC -o
.libs/via_mode.o \
-save-temps
--
Summary: -fschedule-insns -O2 -march=athlon cause compilation
error
Product: gcc
Version: 3.4.6
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: master_up at post dot cz
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27432
next reply other threads:[~2006-05-04 17:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 17:26 master_up at post dot cz [this message]
2006-05-04 17:29 ` [Bug c/27432] " master_up at post dot cz
2006-05-04 17:30 ` master_up at post dot cz
2006-05-04 17:30 ` [Bug target/27432] " pinskia at gcc dot gnu dot org
2006-05-29 22:21 ` pinskia at gcc dot gnu dot org
2006-05-30 10:07 ` master_up at post dot cz
2007-10-16 10:55 ` pinskia at gcc dot gnu dot org
2007-10-16 11:13 ` pinskia at gcc dot gnu dot org
2008-11-30 17:56 ` rguenth at gcc dot gnu dot org
2009-09-17 12:04 ` 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-27432-12628@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).