Since GCC 9, C++17 support is no longer experimental. It was too late
to change the default C++ dialect to C++17 in GCC 10, but I think now
it's time to pull the trigger (C++14 was made the default in GCC 6.1).
We're still missing two C++17 library features, but that shouldn't stop
us. See
Current cfns.h includes register-qualified variables and that wouldn't
play well when bootstrapping with GCC that uses the C++17 dialect,
because 'register' was removed in C++17. Regenerating it using the
command specified in cfns.h luckily cleaned this up.
Bootstrapped/regtested on
This patch resolves DR 1512 (and, by turn, DR 583). This entails:
1) Relational pointer comparisons against null pointer constants have
been made ill-formed:
void f(char *p) {
if (p > 0)
// ...
}
was always invalid in C but was -- accidentally -- allowed in C++.
2)
This feels extremely obscure but at least it's an opportunity to fix the
comments. P0002R1 removed deprecated operator++(bool) in C++17 so let's
avoid adding a builtin overload candidate for ++ when the type is bool.
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
* call.c
Hi,
This patch fixes PR95155, which prevented the D front-end in gcc-9 from
being able to bootstrap a self-hosted D compiler.
The Semantic (pass 1) analysis for classes is handled by
ClassDeclaration::semantic. For a given class, this method may be ran
multiple times in order to resolve forward
Hi,
The last change to the bindings removed the st_pad3 field from the wrong
struct. It should have been stat64_t that needed updating instead.
Patch backported from r10-8066, committed to gcc-9 branch.
Iain.
---
libphobos/ChangeLog
PR d/90719
*
On Fri, May 15, 2020 at 11:21:30AM +0200, Uros Bizjak wrote:
> On Wed, May 13, 2020 at 5:58 PM H.J. Lu wrote:
>
> > > > > The question is, why STV pass creates its funny sequence? The original
> > > > > sequence should be easily solved by storing DImode from XMM register
> > > > > and (with
On May 16, 2020 11:42:02 AM GMT+02:00, Erick Ochoa
wrote:
>Fixes documentation for gimple_assign functions
>
>This patch corrects the documented function signatures of
>gimple_assign*
>functions.
OK.
Richard.
>ChangeLog:
>
>2020-05-16 Erick Ochoa
>
> * gcc/gimple.h
On May 16, 2020 11:41:51 AM GMT+02:00, Erick Ochoa
wrote:
>Adds wrapper for gimple_return_retval to accept gimple*
>
>Most functions interact with GIMPLE IL using arguments of type gimple*.
>
>Functions interacting with GIMPLE_RETURN instructions still use
>greturn*
>types as arguments. This
Hi!
On Sat, May 16, 2020 at 09:46:15AM -0500, Peter Bergner wrote:
> On 5/13/20 11:22 AM, Joel Brobecker wrote:
> > Would someone mind reviewing this patch, please?
> You should always CC the PPC maintainers on PPC patches.
> I've CC'd both Segher and David.
Thanks Peter. Yes, I hadn't seen
On 16/05/2020 01:42, Witold Baryluk via Gcc-patches wrote:
> Adds support for DMGL_RET_POSTFIX in D demangler, so it shows the type
> of the declared variable, or function return type. Postfix notation is
> used with space.
>
Hi,
Thanks for your contribution, it would be good to have a
On Sat, 16 May 2020, Gerald Pfeifer wrote:
> This brought some problems with that page which I addressed per the
> follow-up patch below.
Some more, notably three cases of ... => ...,
note that closing .
Pushed.
Gerald
commit bb406fa02b9a9c47861bc2246513c198bffc90bb
Author: Gerald Pfeifer
On Fri, 15 May 2020, Kyrylo Tkachov wrote:
>> From: Srinath Parvathaneni
>> M-profile related changes in GCC-10.
> Ok.
This brought some problems with that page which I addressed per the
follow-up patch below.
(I am not sure I would have introduced a one-element list, but kept
that and just
On 5/13/20 11:22 AM, Joel Brobecker wrote:
> Hello,
>
> Would someone mind reviewing this patch, please?
>
> The test explicitly uses -mvsx in the compilation options, so it seems
> reasonable to require powerpc_vsx_ok...
>
> Thank you!
You should always CC the PPC maintainers on PPC patches.
Sorry for the empty subject line earlier...
Jason Merrill writes:
> On Fri, May 15, 2020 at 9:47 PM Martin Sebor wrote:
>
>> On 5/15/20 8:08 AM, Richard Sandiford wrote:
>> >> Those are all good examples. Mind putting that into a patch
>> >> for the coding conventions?
>> > How's this? I
Fixes documentation for gimple_assign functions
This patch corrects the documented function signatures of gimple_assign*
functions.
ChangeLog:
2020-05-16 Erick Ochoa
* gcc/gimple.h (gimple_assign_rhs_code): Fix signature
(gimple_assign_rhs_class): same
Adds wrapper for gimple_return_retval to accept gimple*
Most functions interact with GIMPLE IL using arguments of type gimple*.
Functions interacting with GIMPLE_RETURN instructions still use greturn*
types as arguments. This patch adds wrappers around functions taking
greturn* as inputs. The
On Jan 10 2020, Stam Markianos-Wright wrote:
> diff --git a/gcc/testsuite/gcc.target/arm/bfloat16_vector_typecheck_2.c
> b/gcc/testsuite/gcc.target/arm/bfloat16_vector_typecheck_2.c
> new file mode 100644
> index 000..16669dcf009
> --- /dev/null
> +++
On May 15, 2020 11:53:42 PM GMT+02:00, Jason Merrill wrote:
>On 5/15/20 2:21 PM, Richard Biener wrote:
>> On May 15, 2020 7:30:38 PM GMT+02:00, Jason Merrill
> wrote:
>>> On Fri, May 15, 2020 at 3:15 AM Richard Biener
>>>
>>> wrote:
>>>
> +# When bootstrapping with GCC, build stage 1 in
19 matches
Mail list logo
