Merge branch 'releases/gcc-15' into devel/omp/gcc-15

Merge up to r15-10454-g898066855feccb (27th Oct 2025)

diff --cc gcc/builtins.cc
Simple merge

diff --cc gcc/c/c-decl.cc
Simple merge

diff --cc gcc/c/c-typeck.cc
Simple merge

diff --cc gcc/cp/constexpr.cc
Simple merge

diff --cc gcc/cp/cp-tree.h
Simple merge

diff --cc gcc/cp/decl.cc
Simple merge

diff --cc gcc/cp/error.cc
Simple merge

diff --cc gcc/cp/mangle.cc
Simple merge

diff --cc gcc/cp/parser.cc
Simple merge

diff --cc gcc/cp/pt.cc
Simple merge

diff --cc gcc/cp/typeck.cc
Simple merge

diff --cc gcc/doc/extend.texi
Simple merge

diff --cc gcc/doc/invoke.texi
Simple merge

diff --cc gcc/expr.cc
Simple merge

diff --cc gcc/fortran/resolve.cc
Simple merge

diff --cc gcc/fortran/trans-array.cc
Simple merge

diff --cc gcc/fortran/trans-expr.cc
Simple merge

diff --cc gcc/fortran/trans-openmp.cc
Simple merge

diff --cc gcc/gimple-fold.cc
Simple merge

diff --cc gcc/gimple.h
Simple merge

diff --cc gcc/omp-expand.cc
Simple merge

diff --cc gcc/omp-general.cc
Simple merge

diff --cc gcc/omp-low.cc
Simple merge

diff --cc gcc/params.opt
Simple merge

diff --cc gcc/tree-vect-data-refs.cc
Simple merge

diff --cc gcc/tree-vect-stmts.cc
Simple merge

diff --cc libgomp/libgomp.texi
index 6d58b16509aae0a723cd56da93394711096152ac,44be5d7575e74ec464dcdfb1687ee0372e815a5c..d9300498f690af1e3aa20cb2c8b3f5d10c0dbe94
--- 1/libgomp/libgomp.texi
--- 2/libgomp/libgomp.texi
+++ b/libgomp/libgomp.texi
@@@ -6957,15 -6841,16 +6995,17 @@@ a @code{nearest} allocation
  
  Additional notes regarding the traits:
  @itemize
 -@item The @code{pinned} trait is supported on Linux hosts, but is subject to
 -      the OS @code{ulimit}/@code{rlimit} locked memory settings.  It currently
 -      uses @code{mmap} and is therefore optimized for few allocations, including
 -      large data.  If the conditions for numa or memkind allocations are
 -      fulfilled, those allocators are used instead.
 +@item The @code{pinned} trait is supported on Linux hosts, but is usually
 +      subject to the OS @code{ulimit}/@code{rlimit} locked memory settings (see
 +      @ref{Offload-Target Specifics} for exceptions).  The implementation
 +      uses a custom allocator to try to use as few memory pages as possible.
 +      At present, freed pinned memory is not returned to the OS (although it
 +      may be reused by subsequent pinned allocations).
  @item The default for the @code{pool_size} trait is no pool and for every
        (re)allocation the associated library routine is called, which might
-       internally use a memory pool.
+       internally use a memory pool.  Currently, the same applies when a
+       @code{pool_size} has been specified, except that once allocations exceed
+       the the pool size, the action of the @code{fallback} trait applies.
  @item For the @code{partition} trait, the partition part size will be the same
        as the requested size (i.e. @code{interleaved} or @code{blocked} has no
        effect), except for @code{interleaved} when the memkind library is