This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: New type-based pool allocator code miscompiled due to aliasing issue?


On Fri, Jun 12, 2015 at 12:58:12AM +0800, pinskia@gmail.com wrote:
> This is just a bug in the older compiler. There was a change to fix in
> placement new operator.  I can't find the reference right now but this is
> the same issue as that.

I'm not claiming 4.1 is aliasing bug free, there are various known issues in
it.  But, is that the case here?

  empty_var = onepart_pool (onepart).allocate ();
  empty_var->dv = dv;
  empty_var->refcount = 1;
  empty_var->n_var_parts = 0;

doesn't really seem to use operator new at all, so I'd say the bug is in
all the spots that call allocate () method of the pool, but don't really
use operator new.

	Jakub


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]