On Thu, 14 Jun 2018, Bernd Edlinger wrote:
> On 06/14/18 15:43, Richard Biener wrote:
> > On Fri, 8 Jun 2018, Bernd Edlinger wrote:
> >
> >> Hi!
> >>
> >>
> >> This patch converts the splay-tree internals into a template, and makes
> >> the typed_splay_tree template really type-safe. Previously
The following fixes move-sese-region-to-function to not clobber
shared trees when it changes BLOCK references.
Invariant addresses are somewhat special in that they are allowed
to be shared (by the verifier) but are actually copied by
unshare_expr and friends.
Maybe that's something we should c
I am testing the following patch removing sign-conversion stripping
from gimplify_build* (those should vanish anyways...).
Bootstrap & regtest running on x86_64-unknown-linux-gnu.
Richard.
2018-06-15 Richard Biener
PR middle-end/86159
* tree-cfg.c (gimplify_build3): Do not
Hi.
I'm going to install following testes patch. It fixes:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86162
Martin
>From 92c822b43d269717575ab5ea6536d07aaad837b4 Mon Sep 17 00:00:00 2001
From: kelvin
Date: Sun, 14 Jan 2018 05:19:29 +
Subject: [PATCH] Partial backport r256656
libcpp/Change
Am 14. Juni 2018 12:40:19 MESZ schrieb Janne Blomqvist
:
>> >> >Either
>> >> >
>> >> >a) short-circuiting in left-to-right order
>> >> >
>> >> >or
>> >> >
>> >> >b) must evaluate all the arguments in left-to-right order
>> >> >
>> >> >My preference would be for a) as that is what most languages
Am 15. Juni 2018 11:22:44 MESZ schrieb Janus Weil :
but
>>> >> >even b) would be better than leaving it undefined.
>>> >>
>>> >> Agreed.
>>> >>
>>> >> In my opinion the best strategy for gfortran in the current
>>situation
>>> >> would be to apply short-circuiting whenever it can be proven t
Hi,
the motivating example is the following program in GNU C:
void foo (int len)
{
int a = 1;
int b[len];
void bar (void)
{
b[0] = a;
a++;
}
bar ();
}
int main (void)
{
foo (4);
}
If you look at the debug info at -O0 -g, you'll see that that the compiler
generates 2 DIE
On Fri, Jun 15, 2018 at 12:50 PM Eric Botcazou wrote:
>
> Hi,
>
> the motivating example is the following program in GNU C:
>
> void foo (int len)
> {
> int a = 1;
> int b[len];
>
> void bar (void)
> {
> b[0] = a;
> a++;
> }
>
> bar ();
> }
>
> int main (void)
> {
> foo (4);
The if condition in arc_return_address_register which selects the arc
return address is not correct as the brackets are incorect placed. The
issue is signalized in bugzilla 85968.
The patch is committed as obvious.
gcc/
2018-06-15 Claudiu Zissulescu
* config/arc/arc.c (arc_return_addr
Robert Suchanek writes:
> This patch adds -mcrc and -mginv options to pass through them
> to the assembler.
>
> Regards,
> Robert
>
> gcc/ChangeLog:
>
> 2018-06-01 Matthew Fortune
>
> * config/mips/mips.h (ASM_SPEC): Pass through -mcrc, -mno-crc,
> -mginv and -mno-ginv to the as
Description:
* This patch fixes the crash issues faced when using -static-libgcc &
-static-libgo on AIX
On AIX, do not call shared library initializers when linking statically.
This fixes a bug where frame tables are registered twice at runtime, one
time by the shared library initializer
$subject
I mainly need this for evaluation right now but I guess it's useful
to users as well (where a new target hook could give names to sizes,
but well...)
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2018-06-15 Richard Biener
* tree-vect-slp.
Currently GCC inserts ENDBR instruction at entries of all non-static
functions, unless LTO compilation is used. Marking all functions,
which are not called indirectly with nocf_check attribute, is not
ideal since 99% of functions in a program may be of this kind.
This patch adds -mmanual-endbr an
Hi,
these bits started when I realized that in the error messages about
redefined default arguments we were using DECL_SOURCE_LOCATION for the
olddecl and just input_location for newdecl: in the future we'll able to
point at the specific default argument but for the time being we can as
well
On Thu, 2018-06-14 at 17:16 -0500, Segher Boessenkool wrote:
> Hi!
>
> On Tue, Jun 12, 2018 at 03:25:20PM -0500, Will Schmidt wrote:
> > --- a/gcc/testsuite/gcc.target/powerpc/fold-vec-neg-int.c
> > +++ b/gcc/testsuite/gcc.target/powerpc/fold-vec-neg-int.c
> > @@ -1,11 +1,11 @@
> > /* Verify that
Hi.
This is first part of IPA summary conversion clean-up. It removes ::get_create
and
uses ::get for ipa-inline related symbol (and call) summaries. I'm planning to
investigate also other summaries.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
M
A DR approved at the Jacksonville meeting earlier this year.
* doc/xml/manual/intro.xml: Document LWG 2993 change.
* include/bits/refwrap.h (reference_wrapper(_Tp&)): Remove.
(reference_wrapper(_Tp&&)): Remove.
(reference_wrapper<_Up>(_Up&&)): Define new constructor
On 06/15/2018 07:08 AM, Alexander Monakov wrote:
> On Tue, 12 Jun 2018, Martin Liška wrote:
>
>> This is equivalent of gimple.vim file. I'm aware of not full coverage of RTL
>> instructions, but hope it's a good start point.
>
> I think this is nice to have and hope you'll get an OK for both this
Hello,
As suggested in [1], the attached patch removes all definitions and
uses of __ARM_ARCH__ and uses __ARM_ARCH instead. The later is indeed
defined by the preprocessor to the appropriate value.
I ran make check on arm-none-eabi (with A-profile multilib),
arm-none-linux-gnueabi, arm-none-linu
On Jun 12 2018, Tom de Vries wrote:
> I've made the PASS/FAIL id minimal (removed the actual args part), which makes
> it easier to read:
> ...
> PASS: scan-tree-dump: too many arguments
> PASS: scan-tree-dump: too few arguments
> PASS: scan-tree-dump-times: too many arguments
> PASS: scan-tree-d
> Hi.
>
> This is first part of IPA summary conversion clean-up. It removes
> ::get_create and
> uses ::get for ipa-inline related symbol (and call) summaries. I'm planning to
> investigate also other summaries.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Read
What is the status of this patch? You never said it was either approved or
suggested changes?
https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00634.html
--
Michael Meissner, IBM
IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
email: meiss...@linux.ibm.com, phone: +1 (978) 899-4797
On 15/06/18 15:30, Christophe Lyon wrote:
> Hello,
>
> As suggested in [1], the attached patch removes all definitions and
> uses of __ARM_ARCH__ and uses __ARM_ARCH instead. The later is indeed
> defined by the preprocessor to the appropriate value.
>
> I ran make check on arm-none-eabi (with A-
On 06/15/2018 05:05 PM, Andreas Schwab wrote:
> On Jun 12 2018, Tom de Vries wrote:
>
>> I've made the PASS/FAIL id minimal (removed the actual args part), which
>> makes
>> it easier to read:
>> ...
>> PASS: scan-tree-dump: too many arguments
>> PASS: scan-tree-dump: too few arguments
>> PAS
On Jun 15 2018, Tom de Vries wrote:
> Where do you see the duplication?
The problem is actually that dg-final.exp is run multiple times, once
for every parallel execution of the testsuite.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 D
On Thu, 14 Jun 2018, Alexander Monakov wrote:
> However, it is not added to LTO streamed-out symtab, so WPA does not see it.
>
> If the direction looks fine overall, I'll look into getting over this
> streaming hurdle (hints much appreciated).
Well, going down this rabbit hole is a fine exercise,
Hi,
On Fri, Jun 15 2018, Martin Liška wrote:
> Hi.
>
> This is first part of IPA summary conversion clean-up. It removes
> ::get_create and
> uses ::get for ipa-inline related symbol (and call) summaries. I'm planning to
> investigate also other summaries.
>
> Patch can bootstrap on x86_64-linux-
This macro should not be defined unconditionally.
The macro isn't official (it was proposed in P0426R1 but doesn't
appear in SD-6 or the drafts, or the C++2a working paper) so I haven't
added any tests. Ideally we would have negative tests for each feature
test macro, to make sure they aren't def
On 06/15/2018 05:33 PM, Andreas Schwab wrote:
> On Jun 15 2018, Tom de Vries wrote:
>
>> Where do you see the duplication?
>
> The problem is actually that dg-final.exp is run multiple times, once
> for every parallel execution of the testsuite.
Ah, I see. Thanks for noting that.
This patch fi
Hi,
> Since CRC and GINV ASEs have now been committed to binutils, please go
> ahead with this change.
This is now committed as r261635.
Robert
C++20 adds a header, which should define all the library
feature test macros, as well as implementation-specific macros like
_GLIBCXX_RELEASE and __GLIBCXX__.
We should decide whether to implement by simply including
and then adding the feature test macros, or if we
should keep it minimal and
On 15/06/18 16:46 +0100, Jonathan Wakely wrote:
This macro should not be defined unconditionally.
The macro isn't official (it was proposed in P0426R1 but doesn't
appear in SD-6 or the drafts, or the C++2a working paper) so I haven't
added any tests. Ideally we would have negative tests for each
On 12/06/18 20:10 +0100, Jonathan Wakely wrote:
Explicit default constructors are problematic, so this change removes
them from and , as per P0935R0.
* include/bits/random.h (linear_congruential_engine)
(mersenne_twister_engine, subtract_with_carry_engine, random_device)
I for
On Fri, 15 Jun 2018, Martin Liška wrote:
> So you prefer to come up with a plugin folder with the *.vim files?
Yes, the main reason being very simple installation if already using a
plugin manager. A plugin folder may contain a custom ftdetect/foo.vim,
so there's no need to edit .vimrc by hand.
I
On 06/14/2018 02:32 PM, David Malcolm wrote:
> The idea is to later use these macros to mark the
> if (dump_enabled_p ())
> parts of the compiler as cold, in the hope of helping non-PGO builds
> of gcc.
>
> I haven't measured it yet, though.
>
> gcc/ChangeLog:
> * system.h (GCC_LIKELY, GC
On Fri, Jun 15, 2018 at 10:31:26AM -0600, Jeff Law wrote:
> On 06/14/2018 02:32 PM, David Malcolm wrote:
> > The idea is to later use these macros to mark the
> > if (dump_enabled_p ())
> > parts of the compiler as cold, in the hope of helping non-PGO builds
> > of gcc.
> >
> > I haven't measure
On 06/15/2018 10:35 AM, Jakub Jelinek wrote:
> On Fri, Jun 15, 2018 at 10:31:26AM -0600, Jeff Law wrote:
>> On 06/14/2018 02:32 PM, David Malcolm wrote:
>>> The idea is to later use these macros to mark the
>>> if (dump_enabled_p ())
>>> parts of the compiler as cold, in the hope of helping non-P
On 14/06/18 17:51 +0100, Jonathan Wakely wrote:
On 14/06/18 10:46 -0600, Martin Sebor wrote:
On 06/13/2018 10:30 AM, Jonathan Wakely wrote:
The C++ committee has confirmed that passing a null pointer to the
unary basic_string_view constructor is undefined. This removes the check
from our implem
Hi Janne,
What about more complicated expressions like, say, "func() .and. flag .and
func2() .and. flag2" etc.? Can it move all the function calls to the end?
Not at the moment.
Like many of the front-end optimizations, this aims for the easy 80%
which are relatively easy to achieve.
IMHO i
Am 14.06.2018 um 10:38 schrieb Janus Weil:
Also, there are AFAIU other similar weirdness with impure functions.
The
standard allows a compiler to optimize
y = f(x) + f(x)
into
y = 2 * f(x)
even if f is impure, which is totally bonkers. Or even not call f at
all,
if the compiler determines tha
Am 14.06.2018 um 11:55 schrieb Jakub Jelinek:
Or warn users that there is no evaluation ordering between the first and
second operand, that both operands are evaluated and it is unspecified which
is evaluated first? Wouldn't you then just warn all the time? Even without
any impure procedures, y
On Fri, Jun 15, 2018 at 8:06 PM, Thomas Koenig
wrote:
> Hi Janne,
>
> What about more complicated expressions like, say, "func() .and. flag .and
>> func2() .and. flag2" etc.? Can it move all the function calls to the end?
>>
>
> Not at the moment.
>
> Like many of the front-end optimizations, thi
This patch fixes an error in the code generation for vec_pack (vector double,
vector double). As previously implemented, this built-in function translates
to the vpkudum instruction.
This patch causes vec_pack (vector double, vector double) to behave the same as
vec_float2 for the same type si
On Fri, Jun 15, 2018 at 12:22 PM, Janus Weil wrote:
> Am 14. Juni 2018 12:40:19 MESZ schrieb Janne Blomqvist <
> blomqvist.ja...@gmail.com>:
> In Fortran, it still feels like functions as such are second-class
> citizens. People seriously advise against using them. Doesn't really help
> the attra
On 06/15/18 09:07, Richard Biener wrote:
> On Thu, 14 Jun 2018, Bernd Edlinger wrote:
>
>> On 06/14/18 15:43, Richard Biener wrote:
>>> On Fri, 8 Jun 2018, Bernd Edlinger wrote:
>>>
Hi!
This patch converts the splay-tree internals into a template, and makes
the typed_splay
On 6/15/18, Bernd Edlinger wrote:
> On 06/15/18 09:07, Richard Biener wrote:
>> On Thu, 14 Jun 2018, Bernd Edlinger wrote:
>>
>>> On 06/14/18 15:43, Richard Biener wrote:
On Fri, 8 Jun 2018, Bernd Edlinger wrote:
> Hi!
>
>
> This patch converts the splay-tree internals in
On June 15, 2018 8:07:44 PM GMT+02:00, Bernd Edlinger
wrote:
>On 06/15/18 09:07, Richard Biener wrote:
>> On Thu, 14 Jun 2018, Bernd Edlinger wrote:
>>
>>> On 06/14/18 15:43, Richard Biener wrote:
On Fri, 8 Jun 2018, Bernd Edlinger wrote:
> Hi!
>
>
> This patch converts
On Fri, Jun 15, 2018 at 08:27:49PM +0300, Janne Blomqvist wrote:
> On Fri, Jun 15, 2018 at 8:06 PM, Thomas Koenig
> wrote:
>
> >
> > What about more complicated expressions like, say, "func() .and. flag .and
> >> func2() .and. flag2" etc.? Can it move all the function calls to the end?
> >>
> >
>
On Wed, Jun 13, 2018 at 05:25:33PM -0400, Michael Meissner wrote:
> This patch fixes the power8 implementation of copysign for IEEE 128-bit
> floating point. In particular, the way the temporary register was allocated
> did not use the normal GCC conventions of using a clobber with match_scratch.
When I added the non-const basic_string::data() overload I made a
silly mistake in the COW version, failing to "leak" the string (i.e.
unshare it and return a pointer to a uniquely-owned string).
PR libstdc++/86169
* include/bits/basic_string.h [!_GLIBCXX_USE_CXX11_ABI]
(b
On 6/12/18 3:25 PM, Will Schmidt wrote:
> diff --git a/gcc/testsuite/gcc.target/powerpc/fold-vec-neg-int.c
> b/gcc/testsuite/gcc.target/powerpc/fold-vec-neg-int.c
> index 4f35856..4cdcc35 100644
> --- a/gcc/testsuite/gcc.target/powerpc/fold-vec-neg-int.c
> +++ b/gcc/testsuite/gcc.target/powerpc/fo
Hi!
We allow only equality/non-equality comparisons of complex numbers, so
introducing less than or greater or equal than comparison for them from
non-equality ones + division is a bad idea; e.g. the expansion will not
handle those.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for tr
On June 15, 2018 8:59:11 PM GMT+02:00, Jakub Jelinek wrote:
>Hi!
>
>We allow only equality/non-equality comparisons of complex numbers, so
>introducing less than or greater or equal than comparison for them from
>non-equality ones + division is a bad idea; e.g. the expansion will not
>handle those
Hi!
Testcase in the PR is too large to include in the testsuite.
The problem is that DF and RTL cross-jumping aren't really prepared to
handle properly EH landing pads which have in addition to EH incoming edges
some other edges (which is what my patch from a few months ago does in
case we have EH
Hi!
As mentioned in the PR, all traces of this warning option except these
were removed earlier, so the warning option does nothing.
The following patch removes its documentation and makes it clear it does
nothing. Bootstrapped/regtested on x86_64-linux and i686-linux, ok for
trunk/8.2?
2018-06
Hi!
The match.pd framework uses op0 == op1 || operand_equal_p (op0, op1, 0)
style comparisons heavily; the reason why we don't optimize away say
volatile int i;
...
int j = i - i;
into int j = (i, 0);
is only because both the C and C++ FE convert the volatile arguments to
non-volatile ones befor
Hi!
The following testcase ICEs, because store_expr is not prepared to handle
VCE-like assignments (while store_field can handle that).
We already had same mode check for the store_expr when size covers the whole
complex to_rtx, this patch adds a similar check when storing just one half
of it (fir
On Fri, Jun 15, 2018 at 09:06:16PM +0200, Jakub Jelinek wrote:
> The following patch fixes it by making sure we don't have EH landing pads
> that are reachable also by the crossing edges by splitting the EH landing
> pad bb we want to jump into and jumping (EDGE_CROSSING) only to the second
> half,
Hi!
On Thu, Jun 14, 2018 at 08:12:31AM -0700, Carl Love wrote:
> --- a/gcc/testsuite/gcc.target/powerpc/altivec-7.c
> +++ b/gcc/testsuite/gcc.target/powerpc/altivec-7.c
> @@ -85,17 +85,22 @@ int main ()
> /* { dg-final { scan-assembler-times "vpkpx" 2 } } */
> /* { dg-final { scan-assembler-time
On Thu, Jun 14, 2018 at 05:48:42PM -0400, Michael Meissner wrote:
> On Thu, Jun 14, 2018 at 04:27:26PM -0500, Segher Boessenkool wrote:
> > On Mon, Jun 11, 2018 at 07:31:44PM -0400, Michael Meissner wrote:
> > > Since we do not define arithmetic insns for IFmode, other than
> > > negate/absolute va
On 06/15/2018 06:18 PM, Alexander Monakov wrote:
On Fri, 15 Jun 2018, Martin Liška wrote:
So you prefer to come up with a plugin folder with the *.vim files?
Yes, the main reason being very simple installation if already using a
plugin manager. A plugin folder may contain a custom ftdetect/foo
On Fri, Jun 15, 2018 at 01:39:49PM -0500, Segher Boessenkool wrote:
> On Wed, Jun 13, 2018 at 05:25:33PM -0400, Michael Meissner wrote:
> > This patch fixes the power8 implementation of copysign for IEEE 128-bit
> > floating point. In particular, the way the temporary register was allocated
> > di
On Fri, 2018-06-15 at 10:36 -0600, Jeff Law wrote:
> On 06/15/2018 10:35 AM, Jakub Jelinek wrote:
> > On Fri, Jun 15, 2018 at 10:31:26AM -0600, Jeff Law wrote:
> > > On 06/14/2018 02:32 PM, David Malcolm wrote:
> > > > The idea is to later use these macros to mark the
> > > > if (dump_enabled_p (
On Wed, Jun 13, 2018 at 5:05 PM, Jason Merrill wrote:
> On Wed, Jun 13, 2018 at 4:12 PM, Jason Merrill wrote:
>> On Mon, Jun 11, 2018 at 2:38 PM, Jason Merrill wrote:
>>> The fix for 80178 was broken, because I forgot that copy_fn_p is false
>>> for move constructors. As a result, the calling c
On 06/14/2018 02:32 PM, David Malcolm wrote:
> The vectorizer code has numerous instances of:
>
> if (dump_enabled_p ())
> dump_printf_loc (MSG_NOTE, vect_location,
> "=== some message ===\n");
>
> In each case, the dump_printf_loc is a MSG_NODE at vect_location.
>
> I
> Eric, I wonder if sjlj doesn't need a similar fix to the PR86108 patch.
> If it does, I think with the following patch it would trigger a checking
> failure. Not familiar with sjlj EH enough to try it myself.
Yes, it does, so please move the fix to create_forwarder_block instead, after
renamin
This testcase was broken by the lambda rewrite. This turned out to be
because the lambda in the template's default argument had namespace
scope, while the instantiation had function scope, because of
tsubst_default_argument calling push_access_scope and do_pushtag using
the resulting value of curr
> 2018-06-15 Jakub Jelinek
>
> PR middle-end/85878
> * expr.c (expand_assignment): Remove now redundant COMPLEX_MODE_P
> check from first store_expr, use to_mode instead of GET_MODE (to_rtx).
> Only call store_expr for halves if the mode is the same.
>
> * gfortra
On Thu, 14 Jun 2018, Martin Sebor wrote:
> > You can #undef it and then use FILE yourself as a block-scope identifier.
> > I don't think it's at all clear that you can #undef it and then use FILE
> > and expect to get the semantics of the standard type FILE (unlike for
> > standard functions).
>
On Thu, 14 Jun 2018, Michael Meissner wrote:
> Any other libgcc function that has a long double interface should get the
> linker warning that the wrong type was used.
libgcc functions have interfaces corresponding to a particular machine
mode and names that vary depending on that mode - not int
On Fri, 15 Jun 2018, Jakub Jelinek wrote:
> Hi!
>
> The match.pd framework uses op0 == op1 || operand_equal_p (op0, op1, 0)
> style comparisons heavily; the reason why we don't optimize away say
> volatile int i;
> ...
> int j = i - i;
> into int j = (i, 0);
> is only because both the C and C++
On Fri, Jun 15, 2018 at 10:21:26PM +0200, Eric Botcazou wrote:
> > Eric, I wonder if sjlj doesn't need a similar fix to the PR86108 patch.
> > If it does, I think with the following patch it would trigger a checking
> > failure. Not familiar with sjlj EH enough to try it myself.
>
> Yes, it does,
On Thu, Jun 14, 2018 at 08:15:51PM -0400, Michael Meissner wrote:
> On Thu, Jun 14, 2018 at 07:00:52PM -0500, Segher Boessenkool wrote:
> > Hi Mike,
> >
> > On Wed, Jun 13, 2018 at 05:16:37PM -0400, Michael Meissner wrote:
> > > This fixes some of the PowerPC tests that had implicit assumptions ab
On Thu, Jun 14, 2018 at 08:18:42PM -0400, Michael Meissner wrote:
> On Thu, Jun 14, 2018 at 06:25:49PM -0500, Segher Boessenkool wrote:
> > On Wed, Jun 13, 2018 at 05:10:15PM -0400, Michael Meissner wrote:
> > > In addition to the previous patch to aid in transitioning the PowerPC long
> > > double
> So like this (if it passes another bootstrap/regtest together with the
> cfgrtl.c change)? It fixes the testcase too.
>
> 2018-06-15 Jakub Jelinek
>
> PR rtl-optimization/86108
> * bb-reorder.c (create_forwarder_block): Renamed to ...
> (create_eh_forwarder_block): ... thi
On 06/15/2018 02:37 PM, Joseph Myers wrote:
On Thu, 14 Jun 2018, Martin Sebor wrote:
You can #undef it and then use FILE yourself as a block-scope identifier.
I don't think it's at all clear that you can #undef it and then use FILE
and expect to get the semantics of the standard type FILE (unli
When deduction guides are supported by the compiler (i.e. for C++17 and
later) replace two basic_string constructors by constrained function
templates as required by LWG 3076. In order to ensure that the pre-C++17
non-template constructors are still exported from the shared library
define a macro
Hi!
On Fri, Jun 15, 2018 at 12:30:47PM -0500, Kelvin Nilsen wrote:
> This patch fixes an error in the code generation for vec_pack (vector double,
> vector double). As previously implemented, this built-in function translates
> to the vpkudum instruction.
>
> This patch causes vec_pack (vector
On 05/31/2018 01:19 PM, Jonathan Wakely wrote:
This adds incomplete but functional support for std::filesystem and
std::experimental::filesystem on MinGW. In theory there should be no
changes to the existing behaviour for POSIX targets from this patch,
as all the various bugs I found while workin
Use __builtin_memmove for trivially copy assignable types
2018-06-14 Glen Joseph Fernandes
* include/bits/stl_algobase.h
(__is_simple_copy_move): Defined helper.
(__copy_move_a): Used helper.
(__copy_move_backward_a): Likewise.
* testsuite/25_algorithms/
In this testcase, N is only used in the lambda for its constant value,
so it should not be captured. The problem was that we didn't call
mark_rvalue_use on N when instantiating the lambda, because it was
wrapped in a NOP_EXPR converting it to the type of the template
argument. Rather than try to
On June 15, 2018 9:08:05 PM GMT+02:00, Jakub Jelinek wrote:
>Hi!
>
>As mentioned in the PR, all traces of this warning option except these
>were removed earlier, so the warning option does nothing.
>
>The following patch removes its documentation and makes it clear it
>does
>nothing. Bootstrapped
82 matches
Mail list logo
