Mercurial > hg > CbC > CbC_gcc

comparison gcc/doc/gty.texi @ 145:1830386684a0

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
gcc-9.2.0
author anatofuz
date Thu, 13 Feb 2020 11:34:05 +0900
parents 84e7813d76e9
children
comparison
equal deleted inserted replaced
131:84e7813d76e9 145:1830386684a0
1 @c Copyright (C) 2002-2018 Free Software Foundation, Inc. 1 @c Copyright (C) 2002-2020 Free Software Foundation, Inc.
2 @c This is part of the GCC manual. 2 @c This is part of the GCC manual.
3 @c For copying conditions, see the file gcc.texi. 3 @c For copying conditions, see the file gcc.texi.
4 4
5 @node Type Information 5 @node Type Information
6 @chapter Memory Management and Type Information 6 @chapter Memory Management and Type Information
360 referenced. But the memory that the pointer points to is an array of 360 referenced. But the memory that the pointer points to is an array of
361 @code{unsigned int} elements, and the GC must not try to scan it to 361 @code{unsigned int} elements, and the GC must not try to scan it to
362 find pointers to mark or relocate, which is why it is marked with the 362 find pointers to mark or relocate, which is why it is marked with the
363 @code{atomic} option. 363 @code{atomic} option.
364 364
365 Note that, currently, global variables can not be marked with 365 Note that, currently, global variables cannot be marked with
366 @code{atomic}; only fields of a struct can. This is a known 366 @code{atomic}; only fields of a struct can. This is a known
367 limitation. It would be useful to be able to mark global pointers 367 limitation. It would be useful to be able to mark global pointers
368 with @code{atomic} to make the PCH machinery aware of them so that 368 with @code{atomic} to make the PCH machinery aware of them so that
369 they are saved and restored correctly to PCH files. 369 they are saved and restored correctly to PCH files.
370 370