On Thu, Oct 15, 2020 at 11:50:28PM +0200, Jan Hubicka wrote:
> Hi,
> this patch implements the discussed change to fnspecs to make it
> possible to specify parameters that are read and written. In addition
> to original plan I ended up adding 'b' for functions that are barriers
> (since those alia
The code added in r10-6437 caused us to create a CONSTRUCTOR when we're
{}-initializing an aggregate. Then we pass this new CONSTRUCTOR down to
cxx_eval_constant_expression which, if the CONSTRUCTOR isn't TREE_CONSTANT
or reduced_constant_expression_p, calls cxx_eval_bare_aggregate. In
this case
Ed,
In commit r232377 (aka 2be75957b80b640c0aac4356ab861edd0c2f1b9d in the
git repo) you added a new header to the include/precompiled directory.
That wasn't mentioned in the ChangeLog, wasn't in the patch posted to
https://gcc.gnu.org/legacy-ml/libstdc++/2016-01/msg00016.html and
wasn't added to
This patch to the Go frontend stops exporting function type parameter
names. When hashing a function type the parameter names are ignored.
Therefore, we should not write them into the export data. Otherwise,
minor changes in the order in which we process the types can cause the
export data to cha
From: Thomas Rodgers
This should address the cumulative comments (modulo the discussion going
on on the reflector about specification issues/questions).
libstdc++/Changelog:
libstdc++-v3/doc/doxygen/user.cfg.in (INPUT): Add new header.
libstdc++-v3/include/Makefile.am (std_header
101 - 105 of 105 matches
Mail list logo