public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "belyshev at depni dot sinp dot msu dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/21173] [4.0 regression] miscompiled pointer subtraction broke Linux kernel Date: Sat, 23 Apr 2005 12:30:00 -0000 [thread overview] Message-ID: <20050423123028.16909.qmail@sourceware.org> (raw) In-Reply-To: <20050423092333.21173.mikpe@csd.uu.se> ------- Additional Comments From belyshev at depni dot sinp dot msu dot ru 2005-04-23 12:30 ------- // Confirmed on amd64 too, smaller testcase (compile with -O2): void abort (void); char q; void *a[2]; void foo (char *p) { int i; for (i = 0; i < 2; i++) a[i] += p - &q; } int main (void) { int i; foo (&q); for (i = 0; i < 2; i ++) if (a[i]) abort (); return 0; } -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|c |tree-optimization Ever Confirmed| |1 GCC build triplet|i686-pc-linux-gnu | GCC host triplet|i686-pc-linux-gnu | GCC target triplet|i686-pc-linux-gnu | Keywords| |wrong-code Known to fail| |4.0.0 Known to work| |3.4.4 Priority|P2 |P1 Last reconfirmed|0000-00-00 00:00:00 |2005-04-23 12:30:26 date| | Summary|miscompiled pointer |[4.0 regression] miscompiled |subtraction broke Linux |pointer subtraction broke |kernel |Linux kernel Target Milestone|--- |4.0.1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21173
next prev parent reply other threads:[~2005-04-23 12:30 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-23 9:23 [Bug c/21173] New: " mikpe at csd dot uu dot se 2005-04-23 11:56 ` [Bug c/21173] " belyshev at depni dot sinp dot msu dot ru 2005-04-23 12:17 ` azarah at gentoo dot org 2005-04-23 12:30 ` belyshev at depni dot sinp dot msu dot ru [this message] 2005-04-23 12:52 ` [Bug tree-optimization/21173] [4.0/4.1 regression] " belyshev at depni dot sinp dot msu dot ru 2005-04-23 13:18 ` pinskia at gcc dot gnu dot org 2005-04-23 13:24 ` steven at gcc dot gnu dot org 2005-04-23 13:36 ` steven at gcc dot gnu dot org 2005-04-23 13:39 ` steven at gcc dot gnu dot org 2005-04-23 14:59 ` jakub at gcc dot gnu dot org 2005-04-23 15:09 ` dberlin at dberlin dot org 2005-04-23 15:13 ` dberlin at dberlin dot org 2005-04-23 17:19 ` azarah at gentoo dot org 2005-04-23 19:37 ` steven at gcc dot gnu dot org 2005-04-23 23:01 ` stevenb at suse dot de 2005-04-24 9:23 ` stevenb at suse dot de 2005-04-24 15:19 ` dberlin at gcc dot gnu dot org 2005-04-24 15:27 ` dberlin at dberlin dot org 2005-04-25 14:00 ` cvs-commit at gcc dot gnu dot org 2005-04-25 14:03 ` cvs-commit at gcc dot gnu dot org 2005-04-25 14:19 ` cvs-commit at gcc dot gnu dot org 2005-04-25 14:47 ` pinskia at gcc dot gnu dot org 2005-04-25 14:50 ` jakub at gcc dot gnu dot org 2005-04-25 15:18 ` dberlin at dberlin dot org 2005-04-26 12:36 ` dberlin at gcc dot gnu dot org 2005-04-28 2:35 ` belyshev at depni dot sinp dot msu dot ru 2005-04-28 23:38 ` cvs-commit at gcc dot gnu dot org 2005-05-10 17:32 ` pinskia at gcc dot gnu dot org 2005-05-10 22:31 ` pinskia at gcc dot gnu dot org 2005-05-11 10:51 ` pinskia at gcc dot gnu dot org 2005-05-17 11:35 ` pinskia at gcc dot gnu dot org 2005-05-18 6:05 ` pinskia at gcc dot gnu dot org 2005-05-22 18:47 ` pinskia at gcc dot gnu dot org 2005-06-12 13:24 ` pinskia at gcc dot gnu dot 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=20050423123028.16909.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).