public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cnstar9988 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/36079] [4.3/4.4 Regression] cld instruction is not emitted anymore. Date: Thu, 22 May 2008 02:42:00 -0000 [thread overview] Message-ID: <20080522024123.4319.qmail@sourceware.org> (raw) In-Reply-To: <bug-36079-1649@http.gcc.gnu.org/bugzilla/> ------- Comment #12 from cnstar9988 at gmail dot com 2008-05-22 02:41 ------- I have read the discussions on gcc-patches. The patchs: --enable-cld used default on x86 and x86_64. If build gcc 4.3.1 using --enable-cld: when use -m32, gcc use -mcld default. when use -m64, gcc not use -mcld default. If build gcc 4.3.1 using --disable-cld: when compile 32bit or 64bit app, gcc not use -mcld default. Both configure, gcc accept -mcld when compile 32bit/64 bit app, and run well. That's ok for me, Thanks! -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36079
next prev parent reply other threads:[~2008-05-22 2:42 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-29 12:53 [Bug target/36079] New: " ubizjak at gmail dot com 2008-04-29 13:15 ` [Bug target/36079] " ubizjak at gmail dot com 2008-04-29 13:37 ` cnstar9988 at gmail dot com 2008-04-29 14:47 ` [Bug target/36079] [4.3/4.4 Regression] " rguenth at gcc dot gnu dot org 2008-05-05 15:49 ` jsm28 at gcc dot gnu dot org 2008-05-20 5:47 ` ubizjak at gmail dot com 2008-05-20 7:09 ` cnstar9988 at gmail dot com 2008-05-20 8:49 ` cnstar9988 at gmail dot com 2008-05-20 12:52 ` ubizjak at gmail dot com 2008-05-20 15:18 ` cnstar9988 at gmail dot com 2008-05-20 15:25 ` cnstar9988 at gmail dot com 2008-05-20 15:28 ` rguenther at suse dot de 2008-05-21 8:55 ` uros at gcc dot gnu dot org 2008-05-22 2:42 ` cnstar9988 at gmail dot com [this message] 2008-05-23 7:54 ` uros at gcc dot gnu dot org 2008-05-23 8:40 ` ubizjak at gmail dot com 2008-06-10 10:08 ` cnstar9988 at gmail dot com 2008-06-10 10:57 ` rguenther at suse dot de
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=20080522024123.4319.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).