[Bug middle-end/38212] restrict implementation causes wrong-code

2009-06-29 Thread rguenth at gcc dot gnu dot org
--- Comment #5 from rguenth at gcc dot gnu dot org 2009-06-29 12:25 --- Fixed. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED

[Bug middle-end/38212] restrict implementation causes wrong-code

2009-06-29 Thread rguenth at gcc dot gnu dot org
--- Comment #4 from rguenth at gcc dot gnu dot org 2009-06-29 12:20 --- Subject: Bug 38212 Author: rguenth Date: Mon Jun 29 12:20:39 2009 New Revision: 149047 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149047 Log: 2009-06-29 Richard Guenther PR middle-end/38212

[Bug middle-end/38212] restrict implementation causes wrong-code

2009-06-22 Thread rguenth at gcc dot gnu dot org
--- Comment #3 from rguenth at gcc dot gnu dot org 2009-06-22 10:56 --- Mine. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned

[Bug middle-end/38212] restrict implementation causes wrong-code

2008-11-21 Thread rguenth at gcc dot gnu dot org
--- Comment #2 from rguenth at gcc dot gnu dot org 2008-11-21 15:28 --- int __attribute__((noinline)) foo (int *__restrict p, int i) { int *__restrict q = p + i; int v = *(p + i); *p = 1; return v + *q; } extern void abort (void); int main() { int i = 0; if (foo (&i, 0) != 1)

[Bug middle-end/38212] restrict implementation causes wrong-code

2008-11-21 Thread rguenth at gcc dot gnu dot org
--- Comment #1 from rguenth at gcc dot gnu dot org 2008-11-21 13:41 --- Shorter testcase: int __attribute__((noinline)) foo (int *__restrict p, int i) { int *__restrict q = p + i; int v = *q; *p = 1; return v + *q; } extern void abort (void); int main() { int i = 0; if (foo