This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/29272] [4.2 Regression] memcpy optimization causes wrong-code
- From: "pinskia at physics dot uc dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 29 Sep 2006 22:13:34 -0000
- Subject: [Bug middle-end/29272] [4.2 Regression] memcpy optimization causes wrong-code
- References: <bug-29272-10053@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #7 from pinskia at physics dot uc dot edu 2006-09-29 22:13 -------
Subject: Re: [4.2 Regression] memcpy optimization causes wrong-code
>
>
>
> ------- Comment #6 from jakub at gcc dot gnu dot org 2006-09-29 22:04 -------
> Is:
> extern void abort (void);
>
> struct S { struct S *s; } s;
> struct T { struct T *t; } t;
>
> static inline void
> foo (void *s)
> {
> struct T *p = s;
> __builtin_memcpy (&p->t, &t.t, sizeof (t.t));
I think the problem is really is &p->t include an access or not?
I know if p is NULL, this is undefined as &p->t is now have a NULL pointer
access but does that include using memcpy?
-- Pinski
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29272