This is the mail archive of the mailing list for the glibc 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: [PATCH][SPARC] missing membar in niagara2_memcpy

    > Tested on an Athena machine (sparc64x) running sparc64-*-linux-gnu.
    > No new warnings triggered by the patch.
    > No regressions detected.
    Does it really fix anything?
    Are these crashes or data corruptions or thread data visibilty issues
    that you've seen in practice and are cured by this change?

Several system tests of a certain (very data intensive) program crashed
as soon as it started to use multilib/niagara2_memcpy, due to memory
corruption.  They run just fine after this patch is applied.

We also observed that jar would occasionally raise  This was due to the fact the last two bytes
of a buffer were not apparently being copied by memcpy.  Again, this
patch fixes that problem.

    The member is extremely expensive and I avoided it intentionally.

Yes I suspected that, given how carefully that code is written.  We are
aware that membars are painful on the T2 (any membar, because all
flavors are mapped to #Sync) but the risk of overlaps is not only
theoretical in this case, unfortunately :(

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