This is the mail archive of the libc-alpha@sourceware.org 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: RFD - Support for memory tagging in GLIBC

From: Paul Eggert <eggert at cs dot ucla dot edu>
To: Szabolcs Nagy <Szabolcs dot Nagy at arm dot com>, Richard Earnshaw <Richard dot Earnshaw at arm dot com>
Cc: nd <nd at arm dot com>, GNU C Library <libc-alpha at sourceware dot org>
Date: Tue, 10 Sep 2019 07:55:02 -0700
Subject: Re: RFD - Support for memory tagging in GLIBC
References: <8306e032-f980-a409-5239-74629e79d041@arm.com> <bb183d3c-76d3-fbb3-8588-544b5615c2a2@cs.ucla.edu> <99caf4bc-57fc-9a51-478f-254e03045e31@arm.com>

Thanks for the clarification. (Hope you don't mind if I cite your email in oneof my lectures this fall. :-)

SPARC ADI has a 64-byte granule, and Richard's email said there could be anefficiency issue there since I assume malloc's block header is smaller than 64bytes. However, this should be a headache only for the SPARC ADI port and shouldnot be user-visible (except for performance).

Follow-Ups:
- Re: RFD - Support for memory tagging in GLIBC
  - From: DJ Delorie

References:
- RFD - Support for memory tagging in GLIBC
  - From: Richard Earnshaw (lists)
- Re: RFD - Support for memory tagging in GLIBC
  - From: Paul Eggert
- Re: RFD - Support for memory tagging in GLIBC
  - From: Szabolcs Nagy

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