public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/18548] [4.0 Regression] Miscompiles code generated by Gambit-C Scheme->C compiler Date: Sat, 18 Dec 2004 14:03:00 -0000 [thread overview] Message-ID: <20041218140312.26988.qmail@sourceware.org> (raw) In-Reply-To: <20041118185317.18548.lucier@math.purdue.edu> ------- Additional Comments From steven at gcc dot gnu dot org 2004-12-18 14:03 ------- Right... so this is miscompiled: ;; a = MAX_EXPR <b, *(long int *) (a + 1)> but this is not: ;; a = MAX_EXPR <*(long int *) (a + 1), b> Tricky to have a stable test case for this. I suppose we should just force both options of the MAX_EXPR into a reg. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18548
next prev parent reply other threads:[~2004-12-18 14:03 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-18 18:53 [Bug middle-end/18548] New: " lucier at math dot purdue dot edu 2004-11-18 19:05 ` [Bug middle-end/18548] " lucier at math dot purdue dot edu 2004-12-16 14:13 ` [Bug tree-optimization/18548] [4.0 Regression] " belyshev at lubercy dot com 2004-12-17 23:28 ` [Bug middle-end/18548] " belyshev at lubercy dot com 2004-12-17 23:50 ` pinskia at gcc dot gnu dot org 2004-12-18 0:03 ` pinskia at gcc dot gnu dot org 2004-12-18 0:33 ` giovannibajo at libero dot it 2004-12-18 0:38 ` pinskia at gcc dot gnu dot org 2004-12-18 13:54 ` steven at gcc dot gnu dot org 2004-12-18 14:03 ` steven at gcc dot gnu dot org [this message] 2004-12-18 14:38 ` cvs-commit at gcc dot gnu dot org 2004-12-18 14:50 ` roger at eyesopen dot com 2004-12-18 15:07 ` steven at gcc dot gnu dot org 2004-12-18 15:08 ` steven at gcc dot gnu dot org 2004-12-18 15:08 ` steven at gcc dot gnu dot org 2004-12-18 15:28 ` belyshev at lubercy dot com 2004-12-18 20:23 ` lucier at math dot purdue dot edu
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=20041218140312.26988.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).