public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reza dot yazdani at amd dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/38768] -fschedule-insns documentation is wrong for x86 and some other targets Date: Fri, 15 Jan 2010 15:19:00 -0000 [thread overview] Message-ID: <20100115151931.25546.qmail@sourceware.org> (raw) In-Reply-To: <bug-38768-12873@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from reza dot yazdani at amd dot com 2010-01-15 15:19 ------- We used -O2 -fsched-pressure -fschedule-insns to build the cpu2006 bmks on an amd64-linux machine. Thanks for the list of bugs. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38768
prev parent reply other threads:[~2010-01-15 15:19 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-08 17:43 [Bug other/38768] New: man page: -fschedule-insns documentation tim at klingt dot org 2009-01-08 17:44 ` [Bug other/38768] " tim at klingt dot org 2009-01-08 18:27 ` Andrew Thomas Pinski 2009-01-08 18:27 ` pinskia at gmail dot com 2009-01-08 18:31 ` tim at klingt dot org 2009-01-09 20:22 ` [Bug other/38768] -fschedule-insns documentation is wrong for x86 and some other targets pinskia at gcc dot gnu dot org 2010-01-14 22:12 ` reza dot yazdani at amd dot com 2010-01-15 3:31 ` hjl dot tools at gmail dot com 2010-01-15 9:46 ` rguenther at suse dot de 2010-01-15 15:19 ` reza dot yazdani at amd dot com [this message]
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=20100115151931.25546.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).