public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/49104] bootstrap failure on AMD K6-2 with illegal instruction (cmove) in stage2 Date: Sun, 22 May 2011 19:44:00 -0000 [thread overview] Message-ID: <bug-49104-4-MKctAyUD85@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49104-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49104 --- Comment #7 from uros at gcc dot gnu.org 2011-05-22 19:14:54 UTC --- Author: uros Date: Sun May 22 19:14:50 2011 New Revision: 174038 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=174038 Log: PR target/49104 * config/i386/cpuid.h (bit_MMXEXT): New define. libcpp/ChangeLog: 2011-05-22 Uros Bizjak <ubizjak@gmail.com> PR target/49104 * lex.c (init_vectorized_lexer): Do not set "minimum" when __3dNOW_A__ is defined. Check bit_MMXEXT and bit_CMOV to use search_line_mmx. Modified: branches/gcc-4_6-branch/gcc/ChangeLog branches/gcc-4_6-branch/gcc/config/i386/cpuid.h branches/gcc-4_6-branch/libcpp/ChangeLog branches/gcc-4_6-branch/libcpp/lex.c
next prev parent reply other threads:[~2011-05-22 19:35 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-21 18:00 [Bug bootstrap/49104] New: " rfo at gmx dot de 2011-05-22 11:36 ` [Bug bootstrap/49104] " rfo at gmx dot de 2011-05-22 11:38 ` rfo at gmx dot de 2011-05-22 15:01 ` mikpe at it dot uu.se 2011-05-22 18:44 ` ubizjak at gmail dot com 2011-05-22 19:14 ` uros at gcc dot gnu.org 2011-05-22 19:17 ` ubizjak at gmail dot com 2011-05-22 19:44 ` uros at gcc dot gnu.org [this message] 2011-05-22 20:05 ` 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-49104-4-MKctAyUD85@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: 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).