[Bug middle-end/68436] [5 Regression] wrong code on x86_64-linux-gnu

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68436

Andrew Pinski  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #4 from Andrew Pinski  ---
Invalid as mentioned in comment #1 so closing as such.

[Bug middle-end/68436] [5 Regression] wrong code on x86_64-linux-gnu

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68436

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|5.4 |5.5

--- Comment #3 from Richard Biener  ---
GCC 5.4 is being released, adjusting target milestone.

[Bug middle-end/68436] [5 Regression] wrong code on x86_64-linux-gnu

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68436

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|5.3 |5.4

--- Comment #2 from Richard Biener  ---
GCC 5.3 is being released, adjusting target milestone.

[Bug middle-end/68436] [5 Regression] wrong code on x86_64-linux-gnu

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68436

Richard Biener  changed:

   What|Removed |Added

 CC||rguenth at gcc dot gnu.org
   Target Milestone|--- |5.3

--- Comment #1 from Richard Biener  ---
Well, certainly malloc () is not supposed to read from x->sm.sm_buffer if that
is
what it does (not sure, the malloc implementation is not visible).

So I suppose what happens is that alloc_object () allocates from GC, that
GC knows that sm.sm_buffer is a pointer to other GC memory and the call
to malloc () triggers a GC run?

In that case yes, malloc () is not supposed to do GC.  If it does you need
to use -fno-builtin-malloc/free.

I consider this bug invalid.