On 9 May 2017 at 17:14, Nathan Sidwell wrote:
> On 05/09/2017 08:06 AM, Ville Voutilainen wrote:
>>
>> Tested on Linux-x64, not tested with the full suite yet.
>>
>> 2017-05-09 Ville Voutilainen
>>
>> gcc/
>>
>> PR c++/80682
>> * cp/method.c (is_trivially_xible): Reject void type
tbsaunde+...@tbsaunde.org writes:
> From: Trevor Saunders
>
> This allows us to set the capacity of the vector when we construct it,
> and still use a stack buffer when the size is small enough.
>
> gcc/ChangeLog:
>
> 2017-05-09 Trevor Saunders
>
> * genrecog.c (int_set::int_set): Explici
tbsaunde+...@tbsaunde.org writes:
> From: Trevor Saunders
>
> This make the sbitmap version return true if the bit was previously
> unset to make it similar to the bitmap version.
>
> gcc/ChangeLog:
>
> 2017-05-09 Trevor Saunders
>
> * sbitmap.h (bitmap_set_bit): Return bool similar to bi
Here is the updated patch to use gimple_seq_unreachable_p() which scans the
sequence backwards so it bails out earlier in the common case (ie, no call
to __builtin_unreachable). As discussed in the previous thread, we remove
case statement labels from the jump table that lead to unreachable blocks
On Tue, Apr 4, 2017 at 4:46 AM, Andreas Krebbel
wrote:
> On 04/03/2017 06:18 PM, Eric Botcazou wrote:
>>> On S/390 UNITS_PER_WORD is:
>>> 8 with -m64
>>> 4 with -m31
>>> 8 with -m31 -mzarch
>>>
>>> This has been chosen to support use of 64 bit registers also in 32 bit
>>> code. Code compiled with
Changes in v3:
- Merge bodies of type_to_string_with_compare and
print_template_tree_comparison into a new function,
print_template_differences. Use simpler comma-insertion criterion.
- Cleanup assertions in cxx_format_postprocessor::handle.
Would it make sense to rename "m_type_a"/"m_type_b" to
This patch is broken out from the C++ patch, for ease of review.
I believe I can self-approve this one, assuming the other patches
in the kit are OK.
The patch:
- adds the bool and const char ** params to the
pp_format_decoder callback
- adds the format_postprocessor class
- adds the "type-diff"
(unchanged in v3)
Changed in v2: use %qH and %qI rather than %H and %I.
This is the second half of the kit, which uses %qH and %qI throughout
the C++ frontend whenever describing type mismatches between a pair
of %qT.
gcc/cp/ChangeLog:
* call.c (print_conversion_rejection): Replace pairs
On Tue, 2017-05-09 at 10:52 -0400, Nathan Sidwell wrote:
> On 05/09/2017 10:07 AM, David Malcolm wrote:
>
>
> > +static const char *
> > +type_to_string_with_compare (tree type, tree peer, bool verbose,
> > +bool show_color)
> > +{
>
> > + for (int idx = 0; idx < len_max
Hi all,
I am stepping down as the SH backend maintainer for personal reasons.
I might still send tiny SH patches and sh-linux testresults if the HDD
of my SH machine can be recovered. I've moved myself to write after
approval section.
I didn't think that I could be involved with such huge and hi
Loads on RISC-V are sign-extending by default, but we weren't telling
GCC this in our PIC load patterns. This corrects the problem, and adds
a zero-extending pattern as well.
gcc/ChangeLog
2017-05-09 Palmer Dabbelt
* config/riscv/riscv.md (ZERO_EXTEND_LOAD): Define.
* config/ri
> Ping?
Sorry for late reply
> >Hi,
> >
> >This patch fixes an assert failure when linking one LTOed object file
> >having a weak alias with a regular object file containing a strong
> >definition for that same symbol. The patch is twofold:
> >
> >+ do not add an alias to a partition if it is exter
On Tue, May 09, 2017 at 01:44:35PM -0500, Bill Schmidt wrote:
> I forgot to ask -- this fix is needed for GCC 6 and 7 as well. Is this ok
> for backport
> after the usual burn-in?
Sure!
Segher
... forgot to copy in gcc-patches here...
Weitergeleitete Nachricht
Betreff: [patch, fortran] PR 80687, 80696
Datum: Tue, 9 May 2017 23:14:30 +0200
Von: Thomas Koenig
An: fort...@gcc.gnu.org
Hello world,
it appears that using VLAs also caused the strange errors reported
in
Hi!
On Wed, 4 Nov 2015 14:10:29 -0800, Cesar Philippidis
wrote:
> > [...]
>
> Thanks. I've applied this patch to trunk.
> gcc/cp/
> * (cp_parser_oacc_single_int_clause): New function.
> (cp_parser_oacc_clause_vector_length): Delete.
> (cp_parser_omp_clause_num_gangs): D
On Sun, May 7, 2017 at 11:47 PM, Andrew Pinski wrote:
> On Sun, May 7, 2017 at 11:37 PM, Richard Sandiford
> wrote:
>> Really sorry for the breakage. I'd forgotten that this depended on:
>>
>> https://gcc.gnu.org/ml/gcc-patches/2017-03/msg01550.html
Thanks, this does fix my build failures. A
On 05/09/2017 07:04 PM, Martin Sebor wrote:
>>>
>
> -Wassign-enum is a Clang warning too, it just isn't included in
> either -Wall or -Wextra. It warns when a constant is assigned
> to a variable of an enumerated type and is not representable in
> it. I enhanced it for GCC to also warn when the
On 08/05/17 17:51, David Malcolm wrote:
So I think it can work if we add a "needs quoting" flag to the
postprocessing phase, if we need to handle the case where %H and %I
ever appear without 'q' (and have the delayed handling stash that flag,
and do the quoting there).
I'll look at implementing
On Tue, May 09, 2017 at 02:33:00PM -0500, Steven Munroe wrote:
> On Tue, 2017-05-09 at 12:23 -0500, Segher Boessenkool wrote:
> > On Mon, May 08, 2017 at 09:49:57AM -0500, Steven Munroe wrote:
> > > Thus I would like to restrict this support to PowerPC
> > > targets that support VMX/VSX and PowerIS
2017-05-09 18:18 GMT+02:00 Jerry DeLisle :
> On 05/08/2017 02:16 PM, Janus Weil wrote:
>> Hi all,
>>
>> the attached patch fixes an ICE-on-valid problem with finalization by
>> making sure that the finalization procedures are properly resolved.
>>
>> In the test case, the finalizer of the component
Hi!
On Mon, 08 May 2017 21:29:28 +0200, I wrote:
> On Thu, 4 Aug 2016 16:07:00 +0200, I wrote:
> > Ping.
> >
> > On Wed, 27 Jul 2016 12:06:59 +0200, I wrote:
> > > On Mon, 25 Jan 2016 16:09:14 +0100, Jakub Jelinek
> > > wrote:
> > > > On Mon, Jan 25, 2016 at 10:06:50AM -0500, Nathan Sidwell wro
Hi Kelvin,
On Mon, May 08, 2017 at 11:04:59AM -0600, Kelvin Nilsen wrote:
> + /* If any supplied arguments are wider than 32 bits, resolve to
> + 64-bit variant of built-in function. */
> + if ((arg1_mode == TImode) || (arg1_mode == DImode) ||
> + (arg2_mode == TImode) || (ar
From: Trevor Saunders
gcc/ChangeLog:
2017-05-09 Trevor Saunders
* cfganal.c (inverted_post_order_compute): Change argument type
to vec *.
* cfganal.h (inverted_post_order_compute): Adjust prototype.
* df-core.c (rest_of_handle_df_initialize): Adjust.
(
From: Trevor Saunders
gcc/ChangeLog:
2017-05-09 Trevor Saunders
* df-core.c (df_set_blocks): Start using auto_bitmap.
(df_compact_blocks): Likewise.
* df-problems.c (df_rd_confluence_n): Likewise.
* df-scan.c (df_insn_rescan_all): Likewise.
(df_process
From: Trevor Saunders
gcc/ChangeLog:
2017-05-09 Trevor Saunders
* bt-load.c (combine_btr_defs): Use auto_bitmap to manage bitmap
lifetime.
(migrate_btr_def): Likewise.
* cfgloop.c (get_loop_body_in_bfs_order): Likewise.
* df-core.c (loop_post_order_com
From: Trevor Saunders
gcc/ChangeLog:
2017-05-09 Trevor Saunders
* cfganal.c (connect_infinite_loops_to_exit): Adjust.
(depth_first_search::depth_first_search): Change structure init
function to this constructor.
(depth_first_search::add_bb): Rename function to this me
From: Trevor Saunders
gcc/ChangeLog:
2017-05-09 Trevor Saunders
* ddg.c (find_nodes_on_paths): Use auto_sbitmap.
(longest_simple_path): Likewise.
* shrink-wrap.c (spread_components): Likewise.
(disqualify_problematic_components): Likewise.
(emit_common
From: Trevor Saunders
These places where probably trying to use the default bitmap obstack,
but passing 0 to bitmap_initialize actually uses gc allocation. In any
case they are all cleaned up before going out of scope so using
auto_bitmap should be fine.
gcc/ChangeLog:
2017-05-09 Trevor Saund
From: Trevor Saunders
gcc/ChangeLog:
2017-05-09 Trevor Saunders
* tree-ssa-dse.c (dse_dom_walker): Make m_live_byes a
auto_sbitmap.
---
gcc/tree-ssa-dse.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/gcc/tree-ssa-dse.c b/gcc/tree-ssa-dse.c
i
From: Trevor Saunders
gcc/ChangeLog:
2017-05-07 Trevor Saunders
* bitmap.h (class auto_bitmap): New constructor taking
bitmap_obstack * argument.
---
gcc/bitmap.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/gcc/bitmap.h b/gcc/bitmap.h
index 49aec001cb0..2ddeee6bc10 100644
--
From: Trevor Saunders
gcc/ChangeLog:
2017-05-09 Trevor Saunders
* cfganal.c (mark_dfs_back_edges): Replace manual stack with
auto_vec.
(post_order_compute): Likewise.
(inverted_post_order_compute): Likewise.
(pre_and_rev_post_order_compute_fn): Likewis
From: Trevor Saunders
This allows us to set the capacity of the vector when we construct it,
and still use a stack buffer when the size is small enough.
gcc/ChangeLog:
2017-05-09 Trevor Saunders
* genrecog.c (int_set::int_set): Explicitly construct our
auto_vec base class.
*
From: Trevor Saunders
This gets rid of one allocation per bitmap. Often the bitmap_head is
now on the stack, when it isn't its part of some other struct on the
heap instead of being refered to by that struct. On 64 bit platforms
this will increase the size of such structs by 24 bytes, but its a
From: Trevor Saunders
Hi,
this is sort of a grab bag, but mostly improving bitmaps and auto_vec, and then
using them in more places. Individually patches commit messages should explain
in more detail where needed.
patches individually bootstrapped and regtested on x86_64-linux-gnu, ok?
Thank
From: Trevor Saunders
This make the sbitmap version return true if the bit was previously
unset to make it similar to the bitmap version.
gcc/ChangeLog:
2017-05-09 Trevor Saunders
* sbitmap.h (bitmap_set_bit): Return bool similar to bitmap
version of this function.
---
gcc/sbitmap.
From: Trevor Saunders
There's two groups of changes here, first taking a sbitmap &, so that we
can assign null to the pointer after freeing the sbitmap to prevent use
after free through that pointer. Second we define overloads of
sbitmap_free and bitmap_free taking auto_sbitmap and auto_bitmap
r
Hello everyone,
since everybody seems to be submitting patches the last few days, I
thought I might as well :)
Attached is a patch that makes the compiler capable of dealing with
implied do variables in
array slices in data statements.
The copying of the expressions is necessary since
gfc_sim
On 05/09/2017 02:01 PM, Rainer Orth wrote:
Andreas Schwab writes:
I see these regressions on ia64:
FAIL: c-c++-common/Wsizeof-pointer-memaccess2.c -std=gnu++11 (test for
excess errors)
Excess errors:
/usr/local/gcc/gcc-20170508/gcc/testsuite/c-c++-common/Wsizeof-pointer-memaccess2.c:11:53:
wa
For C++17 aggregate bases, we have started adding base fields for
empty bases. The code for calculating whether a class is standard
layout needs to ignore these.
The C++17 mode diagnostic for direct-enum-init1.C was incorrect.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 9a612cc30d4b3ef
66297: C++14 removed the requirement that a constexpr member function
must be a member of a literal class.
70979: We were failing to treat a C++14 lambda as non-literal; they
are only literal with the constexpr lambda addition in C++17.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 187ea3
Hi
A trivial code simplification in a pre-C++11 piece of code.
Ok to commit ?
François
diff --git a/libstdc++-v3/include/bits/stl_algobase.h b/libstdc++-v3/include/bits/stl_algobase.h
index d15be63..a33dde2 100644
--- a/libstdc++-v3/include/bits/stl_algobase.h
+++ b/libstdc++-v3/includ
We used to split the inlined-into block at (= after) the call, and then
remove the call from the first block to insert it in the second.
The removal may cause unnecessary and unrecoverable resetting of debug
insns: we do not generate debug temps for calls.
Avoid the remove-and-reinsert dance by s
On 05/05/2017 15:08, Jonathan Wakely wrote:
On 04/05/17 22:16 +0200, François Dumont wrote:
Hi
Here is the patch to remove the useless _Is_pod_comparator
_Rb_tree_impl template parameter. As this is an ABI breaking change
it is limited to the versioned namespace mode and the patch also bum
Andreas Schwab writes:
> I see these regressions on ia64:
>
> FAIL: c-c++-common/Wsizeof-pointer-memaccess2.c -std=gnu++11 (test for
> excess errors)
> Excess errors:
> /usr/local/gcc/gcc-20170508/gcc/testsuite/c-c++-common/Wsizeof-pointer-memaccess2.c:11:53:
> warning: 'void* __builtin_memcpy(vo
On Tue, 2017-05-09 at 12:23 -0500, Segher Boessenkool wrote:
> Hi!
>
> On Mon, May 08, 2017 at 09:49:57AM -0500, Steven Munroe wrote:
> > Thus I would like to restrict this support to PowerPC
> > targets that support VMX/VSX and PowerISA-2.07 (power8) and later.
>
> What happens if you run it on
Currently, the TDF_foo flags serve 3 purposes:
1) what kind of dump
2) how detailed to print it
3) auxiliary message control
This addresses #1, which currently uses a bit mask of
TDF_{TREE,RTL,IPA}, of which exactly one must be set. The patch changes
things so that these are now an index value
On May 9, 2017, at 9:58 AM, Segher Boessenkool
wrote:
>
> Hi!
>
> On Thu, May 04, 2017 at 04:35:10PM -0500, Bill Schmidt wrote:
>> In an earlier patch, I changed vec_xl and vec_xst to make use of new
>> POWER9 instructions when loading or storing vector short/char values.
>> In so doing, I fail
On 05/09/2017 07:24 AM, Prathamesh Kulkarni wrote:
ping https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00161.html
Thanks,
Prathamesh
On 3 May 2017 at 11:30, Prathamesh Kulkarni
wrote:
On 3 May 2017 at 03:28, Martin Sebor wrote:
On 05/02/2017 11:11 AM, Prathamesh Kulkarni wrote:
Hi,
The att
On Tue, May 9, 2017 at 8:35 PM, Thomas Koenig wrote:
> Hello world,
>
> the attached patch hopefully fixes the build failure on nvptx introduced
> by my recent matmul library patch. It uses malloc/free if VLAs do not
> work.
>
> Thomas S., does this fix the problem?
>
> Tested on x86_64 to make s
Hello world,
the attached patch hopefully fixes the build failure on nvptx introduced
by my recent matmul library patch. It uses malloc/free if VLAs do not
work.
Thomas S., does this fix the problem?
Tested on x86_64 to make sure that the matmul tests still pass;
full regression test still in
Hi!
On Mon, May 08, 2017 at 09:49:57AM -0500, Steven Munroe wrote:
> Thus I would like to restrict this support to PowerPC
> targets that support VMX/VSX and PowerISA-2.07 (power8) and later.
What happens if you run it on an older machine, or as BE or 32-bit,
or with vectors disabled?
> So I pro
Am 09.05.2017 um 12:43 schrieb Andreas Schwab:
On Mai 05 2017, Thomas Koenig wrote:
@@ -227,6 +226,17 @@ sinclude(`matmul_asm_'rtype_code`.m4')dnl
if (m == 0 || n == 0 || k == 0)
return;
+ /* Adjust size of t1 to what is needed. */
+ index_type t1_dim;
+ t1_
On Tue, May 09, 2017 at 09:18:42AM -0700, Jerry DeLisle wrote:
>
> Yes Ok and thanks for patch. The lock_7 is fixed today and I did not see the
> mvbits fail yesterday. Regardlessm unrelated.
>
mvbits_7 is a victim of stupid by non-Fortran committers.
/home/sgk/gcc/gccx/gcc/testsuite/gfortran.d
> Le 9 mai 2017 à 18:15, Fritz Reese a écrit :
>
>> (1) you don’t need the lines (as in "please don’t use them")
>>
>> +
>> +! { dg-final { cleanup-modules "pr80668" } }
>
> I will remove the "dg-final" lines.
>
>>
>> (2) I don’t understand the comments after 'INTEGER,DIMENSION(:),POINTER ::
Hi,
On 4 May 2017 at 11:05, Ramana Radhakrishnan
wrote:
> On Thu, May 04, 2017 at 09:50:42AM +0100, Prakhar Bahuguna wrote:
>
>
>> >
>> > Otherwise ok. Please respin and test with an armhf thumb32 bootstrap
>> > and regression test run.
>> >
>> > regards
>> > Ramana
>>
>> I've respun this patch
On 05/09/2017 08:37 AM, Fritz Reese wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80668
>
> All,
>
> The following fixes a bug exposed in PR 80668 in which the compiler
> attempted to generate an initializer for components of derived types
> with the POINTER attribute when compiling with
On 05/08/2017 02:16 PM, Janus Weil wrote:
> Hi all,
>
> the attached patch fixes an ICE-on-valid problem with finalization by
> making sure that the finalization procedures are properly resolved.
>
> In the test case, the finalizer of the component type was not being
> resolved if the superordina
> (1) you don’t need the lines (as in "please don’t use them")
>
> +
> +! { dg-final { cleanup-modules "pr80668" } }
I will remove the "dg-final" lines.
>
> (2) I don’t understand the comments after 'INTEGER,DIMENSION(:),POINTER ::
> dist’.
(2) Sorry, the comments were meant to show the error t
Hello!
Attached patch enables post-reload compare elimination pass by
providing expected patterns (duplicates of existing patterns with
setters of reg and flags switched in the parallel) for flag setting
arithmetic instructions.
The merge triggers more than 3000 times during the gcc bootstrap,
mo
Hi Mike,
On Fri, May 05, 2017 at 07:43:25PM -0400, Michael Meissner wrote:
> This code does stores in Altivec registers by moving the value to FPR and
> using
> the traditional STFS instruction. However, in looking at the code, I came to
> the conclusion that we could do better (PR 80510) by usi
I just committed a patch at revision r247803 with updated dg-final regexps
(approved by Rich in bugzilla).
Dominique
Hi,
The attached patch adds the following pattern to match.pd
sqrt(x) cmp sqrt(y) -> x cmp y.
and is enabled with -funsafe-math-optimization and -fno-math-errno.
Bootstrapped+tested on x86_64-unknown-linux-gnu.
Cross-tested on arm*-*-*, aarch64*-*-*.
OK for trunk ?
Thanks,
Prathamesh
2017-05-09
Fritz,
Thanks for the quick fix, IMO on the obvious side. Two minor nits:
(1) you don’t need the lines (as in "please don’t use them")
+
+! { dg-final { cleanup-modules "pr80668" } }
(2) I don’t understand the comments after 'INTEGER,DIMENSION(:),POINTER ::
dist’.
TIA
Dominique
PS The failur
As a result of adding a data member to the format_flag_spec
struct my change to enhance -Wformat to warn about poorly quoted
GCC diagnostics managed to break bootstrap for the Cygwin and
Solaris targets, both of which make use of the struct to define
their own printf format extensions.
I committe
On Thu, May 04, 2017 at 07:44:58PM -0400, David Malcolm wrote:
> This patch kit implements two new options to make it easier
> to read diagnostics involving mismatched template types:
> -fdiagnostics-show-template-tree and
> -fno-elide-type.
>
> It adds two new formatting codes: %H and %I whic
On 05/09/2017 09:33 AM, Nick Clifton wrote:
Hi Martin,
Rats! I ran into this when building for sparcv9-solaris2.11 but
didn't look at the cause of the error carefully enough to recognize
it was caused by my change so I just raised 80673 for it. It didn't
occur to me that targets defined their
-fdump-translation-unit is an inscrutably opaque dump. It turned out
that most of the uses of the tree-dump header file was to indirectly get
at dumpfile.h, and the dump_function entry point it had forwarded to a
dumper in tree-cfg.c. The gimple dumper would use its node dumper when
asked for
If we use chkp_generate_extern_var_bounds for void variable just as
for arrays with unknown size, we will create the following gimple seq:
# VUSE <.MEM>
__size_tmp.0 = __builtin_ia32_sizeof (foo);
__size_tmp.1_3 = __size_tmp.0;
However, this will fail in verify_gimple_call:
tree arg = gimple_cal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80668
All,
The following fixes a bug exposed in PR 80668 in which the compiler
attempted to generate an initializer for components of derived types
with the POINTER attribute when compiling with -finit-derived and
-finit-*=*. It is nonsensical for comp
Hi Martin,
> Rats! I ran into this when building for sparcv9-solaris2.11 but
> didn't look at the cause of the error carefully enough to recognize
> it was caused by my change so I just raised 80673 for it. It didn't
> occur to me that targets defined their own format extensions like
> this. W
On 05/09/2017 09:08 AM, Nick Clifton wrote:
Hi Martin,
I am currently unable to build gcc for the x86_64-pc-cygwin target
because gcc/config/i386/msformat-c.c uses the format_flag_spec struct
but it has not been updated with the new field. :-( For example:
gcc/config/i386/msformat-c.
Hi Carl,
On Fri, May 05, 2017 at 02:22:14PM -0700, Carl E. Love wrote:
> This patch adds support for the various vec_neg() builtins.
>
> The patch has been tested on powerpc64le-unknown-linux-gnu (Power 8 LE)
> with no regressions.
>
> Is the patch OK for gcc mainline?
Yes please, thanks!
Seg
On 05/09/2017 09:39 AM, Richard Biener wrote:
On Tue, May 9, 2017 at 3:33 PM, Nathan Sidwell wrote:
I wondered if we'd get sane backtraces and what not, if the optimizer
thought such functions never barfed.
Well, I think you'd either ICE in the first check or can safely CSE the
second.
Do
On Tue, May 9, 2017 at 9:46 AM, Jason Merrill wrote:
> The issue here was that we've been trying to treat C++
> list-initialized temporaries (which are rvalues) the same as C99
> compound literals (which are lvalues). This patch distinguishes
> between them so we can treat them each correctly.
T
Hi Martin,
I am currently unable to build gcc for the x86_64-pc-cygwin target
because gcc/config/i386/msformat-c.c uses the format_flag_spec struct
but it has not been updated with the new field. :-( For example:
gcc/config/i386/msformat-c.c
gcc/config/i386/msformat-c.c:52:1: error
This patch adds runtime support for the OpenACC update if_present
clause. It turned out to require significantly less work to implement
if_present in the runtime. Instead of creating a new API for
GOACC_updated, I exploited the fact that OpenACC no longer uses
GOMP_MAP_FORCE_* data mappings. This a
Hi!
On Thu, May 04, 2017 at 04:35:10PM -0500, Bill Schmidt wrote:
> In an earlier patch, I changed vec_xl and vec_xst to make use of new
> POWER9 instructions when loading or storing vector short/char values.
> In so doing, I failed to enable the existing instruction use for
> -mcpu=power8, so the
On 05/09/2017 10:07 AM, David Malcolm wrote:
+static const char *
+type_to_string_with_compare (tree type, tree peer, bool verbose,
+bool show_color)
+{
+ for (int idx = 0; idx < len_max; idx++)
+{
...
+ if (idx + 1 < len_max)
+ pp_character (pp,
On Mon, 8 May 2017, Volker Reichelt wrote:
> 2017-05-07 Volker Reichelt
>
> PR c/35441
> * c-pretty-print.c (c_pretty_printer::expression): Handle MAX_EXPR,
> MIN_EXPR, EXACT_DIV_EXPR, RDIV_EXPR, LROTATE_EXPR, RROTATE_EXPR.
> (c_pretty_printer::postfix_expression): Hand
Added two new tests. Committed r247797.
Thank you for your review,
Claudiu
Committed r247796.
Thank you for your review,
Claudiu
Committed r247795 including the indicated fixes.
Thank you for your review,
Claudiu
On 05/09/2017 08:06 AM, Ville Voutilainen wrote:
Tested on Linux-x64, not tested with the full suite yet.
2017-05-09 Ville Voutilainen
gcc/
PR c++/80682
* cp/method.c (is_trivially_xible): Reject void types.
testsuite/
PR c++/80682
* g++.dg/ext/is_trivially_c
On 05/09/2017 02:57 AM, Richard Biener wrote:
On Mon, May 8, 2017 at 4:31 PM, Martin Sebor wrote:
On 05/04/2017 10:13 PM, Jeff Law wrote:
On 04/28/2017 04:02 PM, Martin Sebor wrote:
The two options were included in -Wall and enabled for all front
ends but only made to be recognized by the d
On Tue, 9 May 2017, Richard Biener wrote:
> On Fri, 5 May 2017, Christophe Lyon wrote:
>
> > Hi Richard,
> >
> >
> > On 3 May 2017 at 10:19, Richard Biener wrote:
> > >
> > > The following extends the very simplistic cost modeling I added somewhen
> > > late in the release process to, for all
On Fri, 5 May 2017, Christophe Lyon wrote:
> Hi Richard,
>
>
> On 3 May 2017 at 10:19, Richard Biener wrote:
> >
> > The following extends the very simplistic cost modeling I added somewhen
> > late in the release process to, for all unknown misaligned refs, also
> > apply this model for loops
The issue here was that we've been trying to treat C++
list-initialized temporaries (which are rvalues) the same as C99
compound literals (which are lvalues). This patch distinguishes
between them so we can treat them each correctly.
This leaves open the question of how compound literals ought to
On Tue, May 9, 2017 at 3:33 PM, Nathan Sidwell wrote:
> On 05/09/2017 09:19 AM, Richard Biener wrote:
>>
>> On Tue, May 9, 2017 at 3:01 PM, Nathan Sidwell wrote:
>
>
>> Ok, but ... are they not "pure" enough? That is, do we really care to
>> preserve
>> the checking side-effect for example when
Changes in v2:
- pass "quote" as an extra bool argument to the pp_format_decoder
callback, so that we can optionally quote the delayed chunks (with
%qH and %qI)
- use %qH and %qI rather than %H and %I.
- use CLASS_TYPE_P.
- use TYPE_P rather than EXPR_P in arg_to_string to handle non-type template
Changed in v2: use %qH and %qI rather than %H and %I.
This is the second half of the kit, which uses %qH and %qI throughout
the C++ frontend whenever describing type mismatches between a pair
of %qT.
gcc/cp/ChangeLog:
* call.c (print_conversion_rejection): Replace pairs of %qT with
On 9 May 2017 at 16:25, Jakub Jelinek wrote:
>> >> 2017-05-09 Ville Voutilainen
>> >>
>> >>gcc/
>> >>
>> >>PR c++/80682
>> >>* cp/method.c (is_trivially_xible): Reject void types.
>
> No cp/ in cp/ChangeLog entries.
So perhaps
2017-05-09 Ville Voutilainen
cp/
PR c++/8
On 05/09/2017 09:19 AM, Richard Biener wrote:
On Tue, May 9, 2017 at 3:01 PM, Nathan Sidwell wrote:
Ok, but ... are they not "pure" enough? That is, do we really care to preserve
the checking side-effect for example when doing
tree_fits_uhwi (t);
(result unused)?
I wondered about that
Hi,
Here is the latest version of the patch with all comments addressed:
gcc/ChangeLog:
2017-05-09 Alexander Ivchenko
* tree-chkp.c (chkp_get_hard_register_var_fake_base_address):
New function.
(chkp_get_hard_register_fake_addr_expr): Ditto.
(chkp_build_addr_expr): Ad
On Tue, May 09, 2017 at 06:55:12PM +0530, Prathamesh Kulkarni wrote:
> ping https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00135.html
The libgomp patch is ok provided the warning is added.
Though, should it be in -Wall and not say just -Wextra?
Jakub
On Tue, May 09, 2017 at 04:17:07PM +0300, Ville Voutilainen wrote:
> On 9 May 2017 at 16:12, Marc Glisse wrote:
> > On Tue, 9 May 2017, Ville Voutilainen wrote:
> >
> >> Tested on Linux-x64, not tested with the full suite yet.
> >>
> >> 2017-05-09 Ville Voutilainen
> >>
> >>gcc/
> >>
> >>
ping https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00135.html
Thanks,
Prathamesh
On 2 May 2017 at 22:43, Prathamesh Kulkarni
wrote:
> Hi,
> During gcc bootstrap, there's a couple of places where the warning got
> triggered.
> I suppose this wasn't a false positive since enum gomp_schedule_type
>
ping https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00161.html
Thanks,
Prathamesh
On 3 May 2017 at 11:30, Prathamesh Kulkarni
wrote:
> On 3 May 2017 at 03:28, Martin Sebor wrote:
>> On 05/02/2017 11:11 AM, Prathamesh Kulkarni wrote:
>>>
>>> Hi,
>>> The attached patch attempts to add option -Wenu
On Tue, May 9, 2017 at 3:01 PM, Nathan Sidwell wrote:
> Hi,
> For name-lookup cleanup I introduced some accessors that are pure functions
> when we're not checking. I noticed we already had a couple of them, so
> introduced an ATTRIBUTE_NTC_PURE define. It avoid #ifndefs and stray
> semicolons.
On 9 May 2017 at 16:12, Marc Glisse wrote:
> On Tue, 9 May 2017, Ville Voutilainen wrote:
>
>> Tested on Linux-x64, not tested with the full suite yet.
>>
>> 2017-05-09 Ville Voutilainen
>>
>>gcc/
>>
>>PR c++/80682
>>* cp/method.c (is_trivially_xible): Reject void types.
>>
>>te
On Tue, 9 May 2017, Ville Voutilainen wrote:
Tested on Linux-x64, not tested with the full suite yet.
2017-05-09 Ville Voutilainen
gcc/
PR c++/80682
* cp/method.c (is_trivially_xible): Reject void types.
testsuite/
PR c++/80682
* g++.dg/ext/is_trivially_constructible1.C
1 - 100 of 144 matches
Mail list logo
