public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stefaan dot simoens at tiscali dot be" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/14053] second stage build errors (--with-cpu=601) Date: Sat, 21 Feb 2004 02:00:00 -0000 [thread overview] Message-ID: <20040221020057.22494.qmail@sources.redhat.com> (raw) In-Reply-To: <20040206230200.14053.stefaan.simoens@tiscali.be> ------- Additional Comments From stefaan dot simoens at tiscali dot be 2004-02-21 02:00 ------- I've got an Apple PowerMacintosh 7200/75; this has the 601 chip. I don't know if my kernel (2.4.25-rc1 for the moment) is the best kernel to run on a 601; I know my kernel works just fine right now (I compiled the kernel myself; the rest of my system is Mandrake 9.1). The kernel is NOT compiled with the "601 Bug Workaround" (I had previous versions compiled with and without the workaround (which inserts sync and isyncs in before and after some instructions) and my system runs fine with or without the workarounds -- I chose to run without). I learned the 601 has PowerPC and POWER instructions; I'm quite sure my 601 does both. (I think all Mandrake PPC binaries are compiled for PowerPC; but when I compile something myself with --mcpu=601 it runs and executes POWER instructions (like nabs, cfr my other post). So, I don't think the kernel disables the "POWER" instructions. However, I think there are a few problems with -mcpu=601 [I was using this switch to gain the most performance as possible...]. I started my optimization-quest compiling the latest binutils -mcpu=601; the build succeeded; all but 5 (ld) tests succeeded (all tests succeeded without the -mcpu=601). (The binutils I use right now are the binutils without the - mcpu=601). I can't tell for sure the kernel saves and restores the MQ register on "context switch" correctly (how can I tell?). Starting from the "good" assembler code (without -mcpu=601) the 'error' in arith-rand-ll.c enters when I replace the divw/mullw/subf with divs/mfmq. The error doesn't always occur (as far as I can read the code, it uses calculations with random numbers...?) -- I ran the compiled 'bad' code for 20 times and I got 10 times 'Aborted' and the other times the program didn't complain at all -- which makes me conclude that it is an error that only sometimes happens, an exception? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14053
next prev parent reply other threads:[~2004-02-21 2:00 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-02-06 23:02 [Bug c/14053] New: " stefaan dot simoens at tiscali dot be 2004-02-07 2:31 ` [Bug c/14053] " pinskia at gcc dot gnu dot org 2004-02-10 1:36 ` [Bug optimization/14053] " pinskia at gcc dot gnu dot org 2004-02-13 17:30 ` stefaan dot simoens at tiscali dot be 2004-02-13 17:31 ` stefaan dot simoens at tiscali dot be 2004-02-13 17:32 ` stefaan dot simoens at tiscali dot be 2004-02-13 17:33 ` stefaan dot simoens at tiscali dot be 2004-02-13 17:49 ` stefaan dot simoens at tiscali dot be 2004-02-20 21:12 ` stefaan dot simoens at tiscali dot be 2004-02-20 21:51 ` pinskia at gcc dot gnu dot org 2004-02-20 22:03 ` geoffk at geoffk dot org 2004-02-21 2:00 ` stefaan dot simoens at tiscali dot be [this message] 2004-02-25 11:05 ` stefaan dot simoens at tiscali dot be 2004-05-12 12:00 ` stefaan dot simoens at tiscali dot be
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=20040221020057.22494.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: 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).