public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ak at muc dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/19102] [3.4 Regression] -march=pentium3 breaks linux kernel compiles w/ gcc-3_4-branch as of 2004/12/20 Date: Wed, 22 Dec 2004 23:53:00 -0000 [thread overview] Message-ID: <20041222235323.20563.qmail@sourceware.org> (raw) In-Reply-To: <20041221101640.19102.bero@arklinux.org> ------- Additional Comments From ak at muc dot de 2004-12-22 23:53 ------- FWIW i compiled a full 3.3-hammer compiled 2.6.10rc3 x86-64 kernel for suspicious use of %xmm or %mm and there wasn't any. There also is a warning in all 2.6 x86-64 kernels for kernel FPU use at runtime. So at least on x86-64 it doesn't seem to be a real issue in practice. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19102
next prev parent reply other threads:[~2004-12-22 23:53 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-21 10:16 [Bug c/19102] New: " bero at arklinux dot org 2004-12-21 10:18 ` [Bug c/19102] " bero at arklinux dot org 2004-12-21 10:22 ` bero at arklinux dot org 2004-12-21 12:23 ` [Bug target/19102] [3.4 Regression] " belyshev at lubercy dot com 2004-12-21 16:44 ` pinskia at gcc dot gnu dot org 2004-12-21 17:55 ` bero at arklinux dot org 2004-12-21 18:00 ` bero at arklinux dot org 2004-12-22 11:31 ` ebotcazou at gcc dot gnu dot org 2004-12-22 12:08 ` ebotcazou at gcc dot gnu dot org 2004-12-22 12:28 ` ebotcazou at gcc dot gnu dot org 2004-12-22 18:49 ` ebotcazou at gcc dot gnu dot org 2004-12-22 19:12 ` rth at gcc dot gnu dot org 2004-12-22 20:02 ` rth at gcc dot gnu dot org 2004-12-22 20:24 ` ebotcazou at gcc dot gnu dot org 2004-12-22 22:32 ` pinskia at gcc dot gnu dot org 2004-12-22 23:18 ` ebotcazou at gcc dot gnu dot org 2004-12-22 23:27 ` rth at gcc dot gnu dot org 2004-12-22 23:53 ` ak at muc dot de [this message] 2004-12-23 1:31 ` cvs-commit at gcc dot gnu dot org 2004-12-23 1:40 ` rth 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=20041222235323.20563.qmail@sourceware.org \ --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).