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 target/63966] [5 regression] inconsistent operand constraints compiling build libcpp Date: Thu, 20 Nov 2014 10:44:00 -0000 [thread overview] Message-ID: <bug-63966-4-3cAl4mUdIt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63966-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63966 --- Comment #8 from uros at gcc dot gnu.org --- Author: uros Date: Thu Nov 20 10:43:45 2014 New Revision: 217830 URL: https://gcc.gnu.org/viewcvs?rev=217830&root=gcc&view=rev Log: PR target/63966 * lex.c [__i386__ || __x86_64__]: Include system <cpuid.h> for GCC_VERSION < 5000. Modified: trunk/libcpp/ChangeLog trunk/libcpp/lex.c
next prev parent reply other threads:[~2014-11-20 10:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-19 14:41 [Bug bootstrap/63966] New: " ro at gcc dot gnu.org 2014-11-19 14:41 ` [Bug bootstrap/63966] " ro at gcc dot gnu.org 2014-11-19 14:48 ` [Bug target/63966] " rguenth at gcc dot gnu.org 2014-11-19 14:58 ` ubizjak at gmail dot com 2014-11-19 19:28 ` ubizjak at gmail dot com 2014-11-19 21:03 ` ro at CeBiTec dot Uni-Bielefeld.DE 2014-11-20 10:09 ` jakub at gcc dot gnu.org 2014-11-20 10:44 ` uros at gcc dot gnu.org [this message] 2014-11-20 10:50 ` ubizjak at gmail dot com 2014-11-20 11:02 ` ubizjak at gmail dot com 2014-11-20 11:08 ` jakub at gcc dot gnu.org 2014-11-20 11:10 ` ubizjak at gmail dot com 2014-11-20 12:10 ` uros at gcc dot gnu.org 2014-11-20 12:15 ` 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-63966-4-3cAl4mUdIt@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).