public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/27575] New: --enable-memory-tagging doesn't work with --enable-tunables=no Date: Sat, 13 Mar 2021 13:52:30 +0000 [thread overview] Message-ID: <bug-27575-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27575 Bug ID: 27575 Summary: --enable-memory-tagging doesn't work with --enable-tunables=no Product: glibc Version: 2.33 Status: NEW Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: hjl.tools at gmail dot com CC: carlos at redhat dot com, rearnsha at arm dot com, skpgkp2 at gmail dot com Target Milestone: --- commit 3784dfc0985fc0185cdc79428f624cdd1e03eabf Author: Richard Earnshaw <rearnsha@arm.com> Date: Mon Dec 21 15:03:03 2020 +0000 malloc: Basic support for memory tagging in the malloc() family This patch adds the basic support for memory tagging. Various flavours are supported, particularly being able to turn on tagged memory at run-time: this allows the same code to be used on systems where memory tagging support is not present without neededing has +#ifdef USE_MTAG + if ((TUNABLE_GET_FULL (glibc, mem, tagging, int32_t, NULL) & 1) != 0) which fails to build with --enable-tunables=no. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-03-13 13:52 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-13 13:52 hjl.tools at gmail dot com [this message] 2024-05-01 18:09 ` [Bug build/27575] " adhemerval.zanella at linaro dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-27575-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).