[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Intel mpx
From: |
Bruno Haible |
Subject: |
Re: Intel mpx |
Date: |
Sun, 04 Feb 2018 02:36:47 +0100 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-104-generic; KDE/5.18.0; x86_64; ; ) |
> I was just setting up a build of gnulib with
>
> CC="gcc -mmpx -fcheck-pointer-bounds"
> CXX="g++ -mmpx -fcheck-pointer-bounds"
The build completed. It did not report any problems, except for
test-fprintf-posix2 and test-printf-posix2, which go into an endless
SIGSEGV loop right at
arg = atoi (argv[1]);
(apparently because the malloc() which is needed to allocate the memory
for bounds fails).
Bruno
- Re: malloca, freea are not thread-safe, (continued)
- Re: malloca, freea are not thread-safe, Bruno Haible, 2018/02/02
- Re: malloca, freea are not thread-safe, Paul Eggert, 2018/02/02
- Re: malloca, freea are not thread-safe, Bruno Haible, 2018/02/02
- Re: malloca, freea are not thread-safe, Paul Eggert, 2018/02/04
- Re: malloca, freea, and Intel MPX, Bruno Haible, 2018/02/03
- Re: malloca, freea, and Intel MPX, Paul Eggert, 2018/02/04
- Re: malloca, freea, and Intel MPX, Bruno Haible, 2018/02/04
- Re: malloca, freea, and Intel MPX, Paul Eggert, 2018/02/04
- Re: malloca, freea are not thread-safe, Florian Weimer, 2018/02/03
- Re: malloca, freea are not thread-safe, Bruno Haible, 2018/02/03
- Re: Intel mpx,
Bruno Haible <=
- Re: malloca, freea are not thread-safe, Paul Eggert, 2018/02/04