public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Erwin dot Unruh at fujitsu-siemens dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/23650] Scheduler does not handle zero_extract correctly Date: Tue, 20 Sep 2005 07:22:00 -0000 [thread overview] Message-ID: <20050920072244.31344.qmail@sourceware.org> (raw) In-Reply-To: <20050831093304.23650.Erwin.Unruh@fujitsu-siemens.com> ------- Additional Comments From Erwin dot Unruh at fujitsu-siemens dot com 2005-09-20 07:22 ------- Created an attachment (id=9780) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9780&action=view) complete testcase (corrected) My first try on the testcase depends on the endianess. S/390 is big endian, intel is little endian. This revised testcase avoids this dependency. It runs correctly on intel (-O0 or -O3). -- What |Removed |Added ---------------------------------------------------------------------------- Attachment #9773 is|0 |1 obsolete| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23650
next prev parent reply other threads:[~2005-09-20 7:22 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-31 9:40 [Bug rtl-optimization/23650] New: " Erwin dot Unruh at fujitsu-siemens dot com 2005-08-31 12:32 ` [Bug rtl-optimization/23650] " pinskia at gcc dot gnu dot org 2005-08-31 12:55 ` Erwin dot Unruh at fujitsu-siemens dot com 2005-08-31 14:45 ` rguenth at gcc dot gnu dot org 2005-08-31 14:48 ` bonzini at gcc dot gnu dot org 2005-08-31 15:00 ` rguenth at gcc dot gnu dot org 2005-09-02 9:08 ` Erwin dot Unruh at fujitsu-siemens dot com 2005-09-19 12:26 ` Erwin dot Unruh at fujitsu-siemens dot com 2005-09-19 17:57 ` rguenth at gcc dot gnu dot org 2005-09-20 7:22 ` Erwin dot Unruh at fujitsu-siemens dot com [this message] [not found] <bug-23650-4@http.gcc.gnu.org/bugzilla/> 2012-01-11 14:23 ` rguenth at gcc dot gnu.org 2013-03-20 0:48 ` pinskia at gcc dot gnu.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=20050920072244.31344.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).