Bug 27575 - --enable-memory-tagging doesn't work with --enable-tunables=no
Summary: --enable-memory-tagging doesn't work with --enable-tunables=no
Status: RESOLVED FIXED
Alias: None
Product: glibc
Classification: Unclassified
Component: build (show other bugs)
Version: 2.33
: P2 normal
Target Milestone: 2.37
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-13 13:52 UTC by H.J. Lu
Modified: 2024-05-01 18:09 UTC (History)
4 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description H.J. Lu 2021-03-13 13:52:30 UTC 
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.
Comment 1 Adhemerval Zanella 2024-05-01 18:09:31 UTC 
Fixed on 2.37 (33237fe83d553dff111915024c9670adc3f06048), the  --enable-tunables is no longer available.