On Thu, Jun 26, 2014 at 07:43:55AM +0200, Marc Glisse wrote:
+ if (compute_type == TREE_TYPE (type)
+ !VECTOR_INTEGER_TYPE_P (TREE_TYPE (rhs2)))
+{
+ optab oplv, opl, oprv, opr, opo;
+ oplv = optab_for_tree_code (LSHIFT_EXPR, type, optab_vector);
+
On June 26, 2014 12:03:21 AM CEST, Martin Jambor mjam...@suse.cz wrote:
Hi,
On Wed, Jun 25, 2014 at 03:14:31PM -0600, Jeff Law wrote:
On 06/24/14 14:19, Martin Jambor wrote:
On Mon, Jun 23, 2014 at 03:35:01PM +0200, Bernd Edlinger wrote:
Hi Martin,
Well actually, I am not sure if we ever
On 26 June 2014 05:03, Jeff Law l...@redhat.com wrote:
On 06/25/14 08:44, Richard Earnshaw wrote:
On 23/06/14 07:58, Zhenqiang Chen wrote:
Hi,
Swapping operands in a ccmp will lead to illegal instructions. So the
patch disables it in simplify_while_replacing.
The patch is separated from
On 25 June 2014 22:44, Richard Earnshaw rearn...@arm.com wrote:
On 23/06/14 07:58, Zhenqiang Chen wrote:
Hi,
Swapping operands in a ccmp will lead to illegal instructions. So the
patch disables it in simplify_while_replacing.
The patch is separated from
On Wed, Jun 25, 2014 at 4:21 PM, Teresa Johnson tejohn...@google.com wrote:
On Tue, May 13, 2014 at 8:19 AM, Xinliang David Li davi...@google.com wrote:
On Tue, May 13, 2014 at 1:39 AM, Richard Biener
richard.guent...@gmail.com wrote:
On Fri, May 9, 2014 at 5:54 PM, Teresa Johnson
GCC provides its own version of stdatomic.h since GCC 4.9. Here we
have:
#define atomic_load_explicit(PTR, MO)\
__extension__\
({\
__auto_type __atomic_load_ptr = (PTR);\
Hi,
On Thu, 26 Jun 2014 08:43:46, Richard Biener wrote:
On June 26, 2014 12:03:21 AM CEST, Martin Jambor mjam...@suse.cz wrote:
Hi,
On Wed, Jun 25, 2014 at 03:14:31PM -0600, Jeff Law wrote:
On 06/24/14 14:19, Martin Jambor wrote:
On Mon, Jun 23, 2014 at 03:35:01PM +0200, Bernd Edlinger wrote:
On Wed, 25 Jun 2014, Jeff Law wrote:
On 06/25/14 08:05, Richard Biener wrote:
This removes restrictions in DOM cprop_operand that inhibit
some optimizations. The volatile pointer thing is really realy
old and no longer necessary while the loop-depth consideration
is only valid for
This patch factors expression checking for GIMPLE.
Generates code as:
if (TREE_CODE (opname) == SSA_NAME)
{
gimple def_stmt = SSA_NAME_DEF_STMT (opname);
if (is_gimple_assign (def_stmt))
{
if (gimple_assign_rhs_code (def_stmt) == expr-code1)
{
}
if
Ping x2.
On 14/6/20 2:24 PM, Chung-Lin Tang wrote:
Ping.
On 2014/6/9 10:03 PM, Chung-Lin Tang wrote:
Hi Richard,
As we talked about earlier, here's a patch to add a compiler option to
work around Cortex-A9 MPCore errata 761319:
On Thu, 26 Jun 2014, Richard Biener wrote:
On Wed, 25 Jun 2014, Jeff Law wrote:
On 06/25/14 08:05, Richard Biener wrote:
This removes restrictions in DOM cprop_operand that inhibit
some optimizations. The volatile pointer thing is really realy
old and no longer necessary while
On Thu, Jun 26, 2014 at 08:10:15AM +0200, Jakub Jelinek wrote:
+compute_type = get_compute_type (LSHIFT_EXPR, opl, type);
+if (compute_type == TREE_TYPE (type)
+|| compute_type != get_compute_type (RSHIFT_EXPR, opr, type)
+|| compute_type !=
Hi Guys,
I am checking in the patch below to fix a small typo in the
description of the RX vector function attribute.
Cheers
Nick
gcc/ChangeLog
2014-06-26 Nick Clifton ni...@redhat.com
* doc/extend.texi (Function Attributes): Fix typo in description
of RX vector
On Thu, 26 Jun 2014, Richard Biener wrote:
On Thu, 26 Jun 2014, Richard Biener wrote:
On Wed, 25 Jun 2014, Jeff Law wrote:
On 06/25/14 08:05, Richard Biener wrote:
This removes restrictions in DOM cprop_operand that inhibit
some optimizations. The volatile pointer thing
Hi Guys,
I am applying the patch below as an obvious fix for a typo in the
check_effective_target_trapping proc in the testsuite's
target-supports.exp file.
Cheers
Nick
gcc/testsuite/ChangeLog
2014-06-26 Nick Clifton ni...@redhat.com
* lib/target-supports.exp
Hi Guys,
I am checking in the patch below to remove a redundant assert, now
that DECL_SECTION_NAME returns a string rather than a tree.
Cheers
Nick
gcc/ChangeLog
2014-06-26 Nick Clifton ni...@redhat.com
* config/frv/frv.c (frv_in_small_data_p): Remove redundant assert.
Index:
As reported before
https://gcc.gnu.org/ml/gcc-patches/2014-06/msg00213.html
the Solaris signbit implementation for GNU C in iso/math_c99.h gives
warnings with -Wstrict-aliasing, breaking Go bootstrap.
The following patch fixes this along the lines of the current
solaris_math_8 fix.
On 26/06/14 15:50, Jakub Jelinek wrote:
On Thu, Jun 26, 2014 at 11:06:26AM +1000, Kugan wrote:
Since our aim is to perform single bit checks, why don’t we just use
this representation internally (i.e. _rtx-unchanging = 1 if SRP_SIGNED
and _rtx-volatil = 1 if SRP_UNSIGNED). As for
Hello!
Attached patch handles (barrier) RTXes that can be reached when
__builtin_trap builtin is used.
2014-06-26 Uros Bizjak ubiz...@gmail.com
PR target/61586
* config/alpha/alpha.c (alpha_handle_trap_shadows): Handle BARRIER RTX.
testsuite/ChangeLog:
2014-06-26 Uros Bizjak
On Thu, Jun 26, 2014 at 07:41:22PM +1000, Kugan wrote:
2014-06-26 Kugan Vivekanandarajah kug...@linaro.org
* calls.c (precompute_arguments): Use new SUBREG_PROMOTED_SET
instead of SUBREG_PROMOTED_UNSIGNED_SET
Missing full stop.
--- a/gcc/cfgexpand.c
+++ b/gcc/cfgexpand.c
@@
Kugan kugan.vivekanandara...@linaro.org writes:
@@ -5203,24 +5203,25 @@ store_expr (tree exp, rtx target, int call_param_p,
bool nontemporal)
== TYPE_PRECISION (TREE_TYPE (exp)))
{
if (TYPE_UNSIGNED (TREE_TYPE (exp))
- != SUBREG_PROMOTED_UNSIGNED_P
On 25/06/14 21:47 +0200, François Dumont wrote:
I would like to finally propose this patch before the one on
_Rb_tree, as a separate one.
I have adopted the same evolution on the tracker_allocator with
even a perfect forwarding constructor to allow its usage on top of
the
On Thu, Jun 26, 2014 at 12:12:03PM +0200, Jakub Jelinek wrote:
@@ -5234,14 +5235,14 @@ store_expr (tree exp, rtx target, int call_param_p,
bool nontemporal)
if (CONSTANT_P (temp) GET_MODE (temp) == VOIDmode)
{
temp = convert_modes (GET_MODE (target), TYPE_MODE
On 19-06-14 18:47, Richard Henderson wrote:
And I forgot to mention it might be worth while to notice simple recursion.
Avoid the early exit path if caller == callee, despite the caller-save info not
being valid.
Richard,
attached patch enables handling of self-recursive functions in the
On Thu, 26 Jun 2014, Jakub Jelinek wrote:
So like this? I've also changed get_compute_type so that it will DTRT
even for -mavx and V4DImode vectors, so e.g. f5/f6/f8 routines in
avx-pr57233.c improve. Also, even for shifts by scalar, if e.g. target
doesn't have shifts by scalar at all, and
This re-structues GENERIC code to the suggested switch-stmt use
which ideally should behave sanely wrt backtracking now
(fingers crossing - we don't have any testcases yet excercising
the GENERIC code-path).
Installed.
Richard.
2014-06-26 Richard Biener rguent...@suse.de
*
On Thu, Jun 26, 2014 at 11:43 AM, Richard Biener
richard.guent...@gmail.com wrote:
On Thu, Jun 26, 2014 at 10:11 AM, Prathamesh Kulkarni
bilbotheelffri...@gmail.com wrote:
This patch factors expression checking for GIMPLE.
Generates code as:
if (TREE_CODE (opname) == SSA_NAME)
{
gimple
Hi Jerry,
The patch looks to be OK for trunk.
Did you check it with the NIST by any chance?
Thanks a lot
Paul
On 26 June 2014 03:58, Jerry DeLisle jvdeli...@charter.net wrote:
Hi,
This bug has nothing to do with negative numbers as in the description.
However, the problem is due to
On 25/06/14 21:56 +0100, Jonathan Wakely wrote:
The other adds an RAII type to help manage pointers obtained from
allocators. The new type means I can remove several ugly try-catch
blocks that are all very similar in structure and have been bothering
me for some time. The new type also makes it
On 26/06/14 12:31 +0100, Jonathan Wakely wrote:
@@ -137,20 +139,12 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
__node_type* __node = _M_nodes;
_M_nodes = _M_nodes-_M_next();
__node-_M_nxt = nullptr;
- __value_alloc_type __a(_M_h._M_node_allocator());
On Thu, Jun 26, 2014 at 01:16:41PM +0200, Marc Glisse wrote:
+ if (compute_type == TREE_TYPE (type)
+ !VECTOR_INTEGER_TYPE_P (TREE_TYPE (rhs2)))
+{
+ optab oplv, opl, oprv, opr, opo;
+ oplv = optab_for_tree_code (LSHIFT_EXPR, type, optab_vector);
+
This patch should be applied to GCC 4.9 and mainline. I do not have
write access, so in case this gets approved, please commit it for me.
gcc/ChangeLog
2014-06-26 Sebastian Huber sebastian.hu...@embedded-brains.de
* config.gcc (nios2-*-*): Add RTEMS support.
*
On Thu, 26 Jun 2014, Jakub Jelinek wrote:
On Thu, Jun 26, 2014 at 01:16:41PM +0200, Marc Glisse wrote:
+if (compute_type == TREE_TYPE (type)
+ !VECTOR_INTEGER_TYPE_P (TREE_TYPE (rhs2)))
+ {
+optab oplv, opl, oprv, opr, opo;
+oplv = optab_for_tree_code
On 26/06/14 00:06 +0100, Jonathan Wakely wrote:
This simplifies some of the test changes in my last patch, I was
misusing the CustomPointerAlloc due to confusion with some uncommitted
changes.
And this fixes the -fno-rtti version of make_shared, I shouldn't have
changed the deleter's parameter
Hello,
I encountered similar issue to PR ipa/61462 where location_t locus =
gimple_location (e-call_stmt) is called for e-call_stmt == NULL (Firefox with
-flto -fdump-ipa-devirt). So that, I decided to introduce new function that is called
for all potentially unsafe locations. I am
DR1579 relaxes [class.copy]/32 so that expressions in return
statements can be looked up as rvalues even when they aren't the same
type as the function return type.
Implementing that seems as simple as removing the restriction on the
types. Tested x86_64-linux, no regressions.
OK for trunk?
We've accumulated some warnings - fixed below.
Richard.
2014-06-26 Richard Biener rguent...@suse.de
* genmatch.c (c_expr::gen_transform): Fix unused parameter.
(dt_simplify::gen_gimple): Mark captures as possibly unused.
(dt_simplify::gen_generic): Likewise.
Hi Gerald,
sorry for the delay, I've been away for a couple of days.
On Tue, 3 Jun 2014, Rainer Orth wrote:
It's been another week, and I still need approval for the build, doc,
and Darwin changes:
https://gcc.gnu.org/ml/gcc-patches/2014-05/msg01860.html
On the doc side, things are
On Thu, Jun 26, 2014 at 3:01 PM, Martin Liška mli...@suse.cz wrote:
Hello,
I encountered similar issue to PR ipa/61462 where location_t locus =
gimple_location (e-call_stmt) is called for e-call_stmt == NULL (Firefox
with -flto -fdump-ipa-devirt). So that, I decided to introduce new
Eric Christopher echri...@gmail.com writes:
If it is just to reach compatibility with the debugger, then I’d rather
either just mandate a certain debugger or autoconf for what the current
debugger supports. As of late people seem to just break the debugging
experience with non-updated gdbs
Only if we could somehow rule out that chars_per_limb can be zero.
Then we know for sure that unsigned overflow must happen, and
the only possible result would be -1.
But at this time, both -1 and 4294967295 are possible.
I see, I thought you meant that the result was -1 statically.
Thanks
The following patch fixes a big inefficiency when using -fdump-tree-all
for large source files. I found that when using this option the
compile time became unreasonably slow, and I traced this to the fact
that dump_begin/dump_end are called around every function/class that
are dumped via
On 06/26/2014 03:20 PM, Richard Biener wrote:
On Thu, Jun 26, 2014 at 3:01 PM, Martin Liška mli...@suse.cz wrote:
Hello,
I encountered similar issue to PR ipa/61462 where location_t locus =
gimple_location (e-call_stmt) is called for e-call_stmt == NULL (Firefox
with -flto
On Thu, Jun 26, 2014 at 3:43 PM, Martin Liška mli...@suse.cz wrote:
On 06/26/2014 03:20 PM, Richard Biener wrote:
On Thu, Jun 26, 2014 at 3:01 PM, Martin Liška mli...@suse.cz wrote:
Hello,
I encountered similar issue to PR ipa/61462 where location_t locus =
gimple_location
On Thu, Jun 26, 2014 at 04:10:03PM +0200, Richard Biener wrote:
On Thu, Jun 26, 2014 at 3:43 PM, Martin Liška mli...@suse.cz wrote:
On 06/26/2014 03:20 PM, Richard Biener wrote:
On Thu, Jun 26, 2014 at 3:01 PM, Martin Liška mli...@suse.cz wrote:
Hello,
I encountered similar
On 06/26/2014 04:18 PM, Jakub Jelinek wrote:
On Thu, Jun 26, 2014 at 04:10:03PM +0200, Richard Biener wrote:
On Thu, Jun 26, 2014 at 3:43 PM, Martin Liška mli...@suse.cz wrote:
On 06/26/2014 03:20 PM, Richard Biener wrote:
On Thu, Jun 26, 2014 at 3:01 PM, Martin Liška mli...@suse.cz wrote:
On Thu, Jun 26, 2014 at 04:27:49PM +0200, Martin Liška wrote:
Well yes - it is of course similar broken in spirit but at least a lot
simpler ;) I'd put a comment there why we do check g for NULL.
But it increases overhead, there are hundreds of gimple_location calls
and most of them will
On 06/25/2014 10:03 AM, Andrew Sutton wrote:
I did a full 3-stage bootstrap which is the default these days.
I'll try --disable-bootstrap and see what happens.
I just did a full bootstrap build and got the same errors. The errors
are correct for C++11, which was enabled by default in this
Bernd, thanks. At this point I think I will avoid opening this can of
worms and not worry about backporting the test case.
Thanks,
Bill
On Wed, 2014-06-18 at 19:18 +0200, Bernd Edlinger wrote:
Hi,
On Wed, 18 Jun 2014 09:56:15, David Edelsohn wrote:
On Tue, Jun 17, 2014 at 6:44 PM, BIll
On 06/26/14 02:58, Richard Biener wrote:
On Thu, 26 Jun 2014, Richard Biener wrote:
On Thu, 26 Jun 2014, Richard Biener wrote:
On Wed, 25 Jun 2014, Jeff Law wrote:
On 06/25/14 08:05, Richard Biener wrote:
This removes restrictions in DOM cprop_operand that inhibit
some optimizations.
Ping.
Original Message
Subject:[PATCH][Ping] Add patch for debugging compiler ICEs
Date: Wed, 11 Jun 2014 18:15:27 +0400
From: Maxim Ostapenko m.ostape...@partner.samsung.com
To: GCC Patches gcc-patches@gcc.gnu.org
CC: Yury Gribov y.gri...@samsung.com, Slava
On Thu, 26 Jun 2014, Sebastian Huber wrote:
gcc/c/ChangeLog
2014-06-26 Sebastian Huber sebastian.hu...@embedded-brains.de
* c-parser.c (c_parser_declaration_or_fndef): Discard all type
qualifiers in __auto_type for atomic types.
(c_parser_typeof_specifier): Discard all
On 06/26/2014 04:29 PM, Jakub Jelinek wrote:
On Thu, Jun 26, 2014 at 04:27:49PM +0200, Martin Liška wrote:
Well yes - it is of course similar broken in spirit but at least a lot
simpler ;) I'd put a comment there why we do check g for NULL.
But it increases overhead, there are hundreds of
On 06/24/2014 10:31 PM, Jeff Law wrote:
On 06/13/14 04:44, mliska wrote:
Hello,
this is core of IPA ICF patchset. It adds new pass and registers all needed
stuff related to a newly introduced interprocedural optimization.
Algorithm description:
In LGEN, we visit all read-only
On 06/26/2014 01:08 AM, Adam Butcher wrote:
Do you want me to apply to 4.9 too?
Please.
Jason
On 06/26/2014 11:15 AM, Ed Smith-Rowland wrote:
I, for one, would like gcc to bootstrap with c++11/c++14. I think we
should be starting to shake down that path. I'm probably not alone in
this.
Agreed.
On the other hand, I don't think c++-concepts branch should be the
leader on this. We
OK.
Jason
On Thu, Jun 26, 2014 at 9:42 AM, Teresa Johnson tejohn...@google.com wrote:
* c-family/c-common.h (get_dump_info): Declare.
* c-family/c-gimplify.c (c_genericize): Use saved dump files.
* c-family/c-opts.c (c_common_parse_file): Begin and end dumps
once around
Hi Honza,
Could you review this patch when you find time?
Thanks
Sri
On Tue, Jun 17, 2014 at 10:42 AM, Sriraman Tallam tmsri...@google.com wrote:
Ping.
On Mon, Jun 9, 2014 at 3:54 PM, Sriraman Tallam tmsri...@google.com wrote:
Ping.
On Mon, May 19, 2014 at 11:25 AM, Sriraman Tallam
On Tue, Jun 3, 2014 at 5:07 PM, Jones, Joel
joel.jo...@caviumnetworks.com wrote:
There is duplicate code for determining whether a load or store
instruction needs acquire or release semantics. This patch removes the
duplicated code and uses a modifying operator to output a/l instead. Since
On Thu, Jun 26, 2014 at 12:40 AM, Richard Biener
richard.guent...@gmail.com wrote:
On Wed, Jun 25, 2014 at 4:21 PM, Teresa Johnson tejohn...@google.com wrote:
On Tue, May 13, 2014 at 8:19 AM, Xinliang David Li davi...@google.com
wrote:
On Tue, May 13, 2014 at 1:39 AM, Richard Biener
Hi Uros,
Could you please review this patch?
Thanks
Sri
On Fri, Jun 20, 2014 at 5:17 PM, Sriraman Tallam tmsri...@google.com wrote:
Patch Updated.
Sri
On Mon, Jun 9, 2014 at 3:55 PM, Sriraman Tallam tmsri...@google.com wrote:
Ping.
On Mon, May 19, 2014 at 11:11 AM, Sriraman Tallam
Now that we're past C++14, C++17(?) features are starting to be added to
the compiler, so we ought to have a switch for them.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit a4480bed3c7aca47203e910dec52d80d61b96b2e
Author: Jason Merrill ja...@redhat.com
Date: Thu Jun 26 12:57:07 2014
N3994 proposes that people writing a range-based for should be able to
leave out the type and have it default to auto. I expect the proposal
to be voted into the working paper at the November standards meeting.
The second patch changes the existing range-for diagnostic from error to
pedwarn,
On 06/26/2014 12:23 PM, Jason Merrill wrote:
We could add -std=c++1z and add it to that, though.
Added.
Jason
Jeff,
thanks for review! I did some passes over the patch before it got to the ML, I
am
happy to have independent opinion.
+@item -fipa-icf
+@opindex fipa-icf
+Perform Identical Code Folding for functions and read-only variables.
+Behavior is similar to Gold Linker ICF optimization. Symbols
On 06/26/2014 02:43 AM, Uros Bizjak wrote:
2014-06-26 Uros Bizjak ubiz...@gmail.com
PR target/61586
* config/alpha/alpha.c (alpha_handle_trap_shadows): Handle BARRIER RTX.
testsuite/ChangeLog:
2014-06-26 Uros Bizjak ubiz...@gmail.com
PR target/61586
*
Hi,
should we do something like this? Tested x86_64-linux.
Thanks,
Paolo.
2014-06-26 Paolo Carlini paolo.carl...@oracle.com
* parser.c (cp_parser_compound_literal_p): New.
(cp_parser_postfix_expression, cp_parser_sizeof_operand): Use it.
Index: parser.c
Hi,
The test case gfortran.dg/nint_2.f90 is XFAILed for certain platforms
because glibc produces wrong results in some cases. The relatively new
powerpc64le-unknown-linux-gnu platform does not have this problem, but
the wild-carding causes it to be XFAILed incorrectly. This patch
changes the
On 26/06/2014 12:33, Jonathan Wakely wrote:
The _GLIBCXX_USE_NOEXCEPT macro expands to nothing in C++03 mode, so
you might as well omit it in the #else branch.
OK for trunk if you make the tracker_allocator comment correct.
Thanks!
Committed with:
// An allocator facade that intercepts
Hello!
Attached patch is needed to fix PR 56858 [1], where alpha used
NOTE_INSN_EH_REGION_BEG and NOTE_INSN_EH_REGION_END notes to handle
its FP traps. After the last RTL exceptions rewrite, those notes are
generated after mach_reorg pass, effectively rendering existing
approach unusable.
In PR
Hi,
I'm afraid something went badly wrong with this commit, I'm seeing tens
of fails. See eg:
https://gcc.gnu.org/ml/gcc-testresults/2014-06/msg02439.html
Paolo.
Some observations on this code (the first is about integration in GCC, the
rest about general good practice for writing robust C libraries for use on
GNU/Linux, where failure to follow such practice is likely to lead to
problems and security advisories in future, so if the code goes in
without
The following is a revamped patch for -Wsizeof-array-argument. Almost two
months back there was an initial attempt by Prathamesh:
https://gcc.gnu.org/ml/gcc-patches/2014-05/msg00142.html, but that patch
never made it in. This version implements the warning for both C and C++
FEs, adds more
On 26/06/14 23:21 +0200, Paolo Carlini wrote:
Hi,
I'm afraid something went badly wrong with this commit, I'm seeing
tens of fails. See eg:
https://gcc.gnu.org/ml/gcc-testresults/2014-06/msg02439.html
It seems that uneq_allocator is no longer copy constructible.
On Thu, Jun 26, 2014 at 4:44 PM, Bill Schmidt
wschm...@linux.vnet.ibm.com wrote:
Hi,
The test case gfortran.dg/nint_2.f90 is XFAILed for certain platforms
because glibc produces wrong results in some cases. The relatively new
powerpc64le-unknown-linux-gnu platform does not have this problem,
From: Trevor Saunders tsaund...@mozilla.com
Hi,
While fixing up the hash_table patch's bustedness here I noticed the code
doesn't make any sense. What it inserts into the hash table will never match
what we try and look up in it. If you want to use hash_table or htab as a map
you need to deal
So is C++14 a done deal with a __cplusplus date and all?
I've been waiting for some news or a trip report from Rapperswil and
have seen nothing on isocpp.
I've been thinking of adding a thing or two to C++1z like clang has -
The Disabling trigraph expansion by default looks easy.
Ed
On 26/06/14 04:29, Paul Richard Thomas wrote:
Hi Jerry,
The patch looks to be OK for trunk.
Did you check it with the NIST by any chance?
Yes, tested fine.
Jerry
From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-
ow...@gcc.gnu.org] On Behalf Of Thomas Preud'homme
Sent: Thursday, June 19, 2014 1:36 PM
Richard, given this issue, I think we should wait a few more days before I
commit
A backported (and fixed of course) version to 4.8 and 4.9.
No
OK.
Jason
On 06/26/2014 09:38 PM, Ed Smith-Rowland wrote:
So is C++14 a done deal with a __cplusplus date and all?
The C++14 draft was finalized at the February meeting in Issaquah; the
ratification process isn't quite done, but I haven't heard any reason to
doubt that it will be done soon. The
The limit can be customized by defining a macro
_GLIBCXX_REGEX_STATE_LIMIT. The default value is 10.
The testcase can be handled if we optimize consecutive quantifiers
(collapse them to one). But cases like (a{100}b){100} can't be
handled still.
We implement range quantifier (foo){n} by
On 06/26/2014 06:25 AM, Chen Gang wrote:
BTW: one linux kernel member found a gcc issue for the latest version
(4.10.0 20140622 or later), but for old version (e.g. 4.10.0 2014060*),
it is OK. It is my chance to fix it (hope can finish within 2014-06-30).
For this issue, at present, I
84 matches
Mail list logo
