Hello, I was just wondering if anybody is currently working on the C++
dynamic array library for c++1z?
> First, a belated follow-up to https://gcc.gnu.org/PR66512 . The bug is
> asking why attribute-const appears to have a weaker effect in C++, compared
> to C. The answer in that bug is that GCC assumes that attribute-const
> function can terminate by throwing an exception.
FWIW there is an equival
Hello,
I'd like to ask for community input regarding __attribute__((const)) (and
"pure", where applicable). My main goal is to clarify unclear cases and
improve existing documentation, if possible.
First, a belated follow-up to https://gcc.gnu.org/PR66512 . The bug is asking
why attribute-const
Hi Guys,
There are lots of things to report in this month's update...
* The G++ ABI has been increased to version 10.
This adds mangling of attributes that affect type identity, such
as ia32 calling convention attributes (e.g. stdcall).
ABI conflicts can be detected with -Wabi
On Thu, Sep 24, 2015 at 11:07 AM, Simon Dardis wrote:
> It seems to me that extending operand_equal_p to deal with the
> MEM_REF/ARRAY_REF case could help.
>
> Your recent change of:
>
> if (TREE_CODE (arg0) == MEM_REF
> && DECL_P (arg1)
> && TREE_CODE (TREE_O
