[PATCH v2] Destroy arguments for _Cilk_spawn calling in the child (PR 80038)

On 2017-04-28 08:42 -0600, Jeff Law wrote: > On 04/28/2017 08:31 AM, Xi Ruoyao wrote: > > Should I prepare (re-diff) a patch for current trunk? > If you want for the trunk, yes. Rediff for current GCC trunk. -- Xi Ruoyao School of Aerospace Science and Technology, Xidian

Re: [PATCH 2/5] c++: New warning option -Wstring-plus-int

On 2017-04-28 14:34 -0600, Jeff Law wrote: > Can you use TYPE_MAIN_VARIANT (type) here rather than building a new type? I'll check the macros. > Formatting problems should be obvious :-) I'll follow the GCC formatting rules. > I think Jason probably needs to chime in on this patch.  I'm not

[PATCH] RISC-V: Don't built 64-bit multilibs on 32-bit targets

We've been telling people that "riscv32-*" and "riscv64-*" are exactly the same toolchain aside from defaults for "-march" and "-mabi", but it appears we were lying. As far as I can tell, binutils doesn't support 64-bit targets when it has been configured for a 32-bit target. This seems to be an

Re: [PATCH 8/8] Enhance documentation of gcov.

On 04/27/2017 03:24 AM, marxin wrote: gcc/ChangeLog: 2017-04-27 Martin Liska * doc/gcov.texi: Enhance documentation of gcov. --- gcc/doc/gcov.texi | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/gcc/doc/gcov.texi b/gcc/doc/gcov.texi index

[PING] Re: [PATCH 1/2] Port Doxygen support script from Perl to Python; add unittests

Ping for these two patches: - https://gcc.gnu.org/ml/gcc-patches/2017-03/msg00909.html - https://gcc.gnu.org/ml/gcc-patches/2017-03/msg00910.html On Thu, 2017-03-16 at 21:51 -0400, David Malcolm wrote: > It's possible to run GCC's sources through Doxygen by setting > INPUT_FILTER

[PATCH] disable -Walloc-size-larger-than and -Wstringop-overflow for non-C front ends (PR 80545)

The two options were included in -Wall and enabled for all front ends but only made to be recognized by the driver for the C family of compilers. That made it impossible to suppress those warnings when compiling code for those other front ends (like Fortran). The attached patch adjusts the

Re: [PATCH] Fix improper combiner optimization of mixed mode vector/scalar expressions (PR 79365)

On 02/03/2017 01:03 PM, Walter Lee wrote: Hi, In looking at PR 79365 I found that the problem is actually in the combiner. The combiner sometimes applies scalar optimizations to vector context where they are invalid. i.e. (a > b) >> 1 can optimize to 0 if ">" is a scalar op but not if it is a

Re: [PATCH,rs600] Add built-in function support for compare bytes instruction

Hi Kelvin, On Fri, Apr 28, 2017 at 11:48:03AM -0600, Kelvin Nilsen wrote: > --- gcc/config/rs6000/rs6000.h(revision 247069) > +++ gcc/config/rs6000/rs6000.h(working copy) > @@ -2717,6 +2717,7 @@ extern int frame_pointer_needed; > aren't in target_flags. */ > #define

Re: [PATCH] add missing overflow check to stpcpy (PR 79222)

On 01/24/2017 08:36 PM, Martin Sebor wrote: In implementing the -Wstringop-overflow warning I missed stpcpy. The attached patch adds the required checking. Given how simple it is, does it qualify for GCC 7 despite stage 4? Martin gcc-79222.diff PR middle-end/79222 - missing

Re: [PATCH] Remove uninitialized reads of is_leaf

On 11/29/2016 12:54 PM, Wilco Dijkstra wrote: Jeff Law wrote: On 11/29/2016 11:39 AM, Wilco Dijkstra wrote: I forgot to ask, would it be reasonable to add an assert to check we're not in a sequence in leaf_function_p? I guess this will trigger on several targets (leaf_function_p is used in

Re: [PATCH 2/5] c++: New warning option -Wstring-plus-int

On 02/22/2017 04:01 AM, Xi Ruoyao wrote: This patch adds warning option -Wstring-plus-int for C++. gcc/ChangeLog: 2017-02-22 Xi Ruoyao * c-family/c-common.h (maybe_warn_string_plus_int): new prototype * c-family/c-warn.h (maybe_warn_string_plus_int):

Re: [PATCH 5/5] New tests for -Wstring-plus-int

On 02/22/2017 04:01 AM, Xi Ruoyao wrote: This patch adds tests for -Wstring-plus-int. gcc/ChangeLog: 2017-02-22 Xi Ruoyao * testsuite/c-c++-common/Wstring-plus-int.c: New test * testsuite/g++.dg/Wstring-plus-int-1.C: New test *

Re: [PATCH 4/5] Document warning option -Wstring-plus-int

On 02/22/2017 04:01 AM, Xi Ruoyao wrote: This patch adds document of -Wstring-plus-int. gcc/ChangeLog: 2017-02-22 Xi Ruoyao * doc/invoke.texi (Warning Options): Document -Wstring-plus-int This is OK for the trunk once all 5 are approved. jeff

Re: [PATCH 3/5] c: New warning option -Wstring-plus-int

On 02/22/2017 04:01 AM, Xi Ruoyao wrote: This patch adds warning option -Wstring-plus-int for C. gcc/ChangeLog: 2017-02-22 Xi Ruoyao * c/c-typeck.c (parser_build_binary_op, build_modify_expr): checking for -Wstring-plus-int --- gcc/c/c-typeck.c | 28

Re: [PATCH 1/5] Move char_type_p prototype into c-common.h

On 02/22/2017 04:01 AM, Xi Ruoyao wrote: This patch moves prototype of char_type_p into c-common.h, so we can use it in c-family/*. gcc/ChangeLog: 2017-02-22 Xi Ruoyao * c-family/c-common.h (char_type_p): New prototype * c/c-typeck.c (char_type_p):

Re: Drop Z from X + Z < Y + Z

On Fri, 28 Apr 2017, Richard Biener wrote: On Fri, Apr 28, 2017 at 1:35 PM, Marc Glisse wrote: Hello, surprisingly, this did not cause any Wstrict-overflow failure. Some of it sounds more like reassoc's job, but it is convenient to handle simple cases in match.pd. I

Re: PR79697: Delete calls to strdup, strndup, realloc if there is no lhs

On 04/25/2017 12:06 AM, Prathamesh Kulkarni wrote: On 25 April 2017 at 02:41, Jeff Law wrote: On 02/25/2017 01:40 AM, Prathamesh Kulkarni wrote: Hi, The attached patch deletes calls to strdup, strndup if it's return-value is unused, and same for realloc if the first arg is

Re: [PATCH][ PR rtl-optimization/79286] Drop may_trap_p exception to testing dominance in update_equiv_regs

On 04/28/17 21:14, Bernd Edlinger wrote: > On 04/28/17 20:46, Jeff Law wrote: >> On 04/28/2017 11:27 AM, Bernd Edlinger wrote: >>> >>> Yes I agree, that is probably not worth it. So I could try to remove >>> the special handling of PIC+const and see what happens. >>> >>> However the

Re: [PATCH][ PR rtl-optimization/79286] Drop may_trap_p exception to testing dominance in update_equiv_regs

On 04/28/17 20:46, Jeff Law wrote: > On 04/28/2017 11:27 AM, Bernd Edlinger wrote: >>> >> >> Yes I agree, that is probably not worth it. So I could try to remove >> the special handling of PIC+const and see what happens. >> >> However the SYMBOL_REF_FUNCTION_P is another story, that part I would

Re: [PATCH 3/8] Simplify representation of locations of a block.

On 04/28/2017 08:01 PM, Pedro Alves wrote: > On 04/28/2017 05:28 PM, Martin Sebor wrote: >> On 04/28/2017 05:47 AM, Nathan Sidwell wrote: > @@ -427,9 +429,31 @@ static void output_lines (FILE *, const source_t *); static char *make_gcov_file_name (const char *, const char *);

Re: [PATCH 3/8] Simplify representation of locations of a block.

On 04/28/2017 01:01 PM, Pedro Alves wrote: On 04/28/2017 05:28 PM, Martin Sebor wrote: On 04/28/2017 05:47 AM, Nathan Sidwell wrote: @@ -427,9 +429,31 @@ static void output_lines (FILE *, const source_t *); static char *make_gcov_file_name (const char *, const char *); static char

Re: [PATCH] have -Wformat-overflow handle -fexec-charset (PR 80503)

On 04/28/2017 12:05 PM, Martin Sebor wrote: So the initialization could be done once per translation unit rather than once per function -- assuming the target character set doesn't change within a translation unit. That seems like it ought to be easy. It is easy. I was going to respond by

Re: [PATCH 3/8] Simplify representation of locations of a block.

On 04/28/2017 05:28 PM, Martin Sebor wrote: > On 04/28/2017 05:47 AM, Nathan Sidwell wrote: >>> @@ -427,9 +429,31 @@ static void output_lines (FILE *, const source_t >>> *); >>> static char *make_gcov_file_name (const char *, const char *); >>> static char *mangle_name (const char *, char *);

Re: [PATCH] Fix fixincludes for canadian cross builds - next try

On 04/20/2017 01:11 PM, Bernd Edlinger wrote: Hi! This is my new attempt to clean up the different cross compiler configurations. It turned out to be a very complicated matter, so I thought it would be better to postpone it to the stage1. In a canadian cross compiler setup we have a different

amended fix for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491

Hello, I've been asked to send the patch against trunk here. Best, christos Index: cpuid.h === --- cpuid.h (revision 247395) +++ cpuid.h (working copy) @@ -235,6 +235,16 @@ return __eax; } +/* Return non-zero if we

Re: [PATCH][ PR rtl-optimization/79286] Drop may_trap_p exception to testing dominance in update_equiv_regs

On 04/28/2017 11:27 AM, Bernd Edlinger wrote: Yes I agree, that is probably not worth it. So I could try to remove the special handling of PIC+const and see what happens. However the SYMBOL_REF_FUNCTION_P is another story, that part I would like to keep: It happens quite often, already w/o

Re: [PATCH] handle enumerated types in -Wformat-overflow (PR 80397)

On 04/26/2017 11:05 AM, Martin Sebor wrote: On 04/24/2017 03:35 PM, Jeff Law wrote: On 04/11/2017 12:57 PM, Martin Sebor wrote: In a review of my fix for bug 80364 Jakub pointed out that to determine whether an argument to an integer directive is of an integer type the gimple-ssa-sprintf pass

Re: [PATCH] Improve RTL ifcvt for empty else_bb (PR rtl-optimization/80491)

On 04/26/2017 05:25 AM, Jakub Jelinek wrote: On Tue, Apr 25, 2017 at 09:31:00PM +0200, Jakub Jelinek wrote: This patch let us search for x's setter earlier in the bb. During testing I found that modified_in_p/modified_in_between_p don't actually take into account calls that could change MEMs,

Re: [PATCH] Improve RTL ifcvt for empty else_bb (PR rtl-optimization/80491)

On 04/25/2017 01:31 PM, Jakub Jelinek wrote: Hi! The following patch is a partial fix for PR80491, an improvement for if-conversion if there is empty else_bb. What we do right now is in that case we only look at the immediately preceeding (non-debug/non-note) instruction before cond_earliest

Re: PR79715: Special case strcpy/strncpy for dse

On 04/24/2017 03:05 AM, Prathamesh Kulkarni wrote: On 1 March 2017 at 13:24, Richard Biener wrote: On Tue, 28 Feb 2017, Jeff Law wrote: On 02/28/2017 05:59 AM, Prathamesh Kulkarni wrote: On 28 February 2017 at 15:40, Jakub Jelinek wrote: On Tue, Feb

Re: [PATCH] have -Wformat-overflow handle -fexec-charset (PR 80503)

On 04/28/2017 10:22 AM, Jeff Law wrote: On 04/27/2017 03:05 PM, Martin Sebor wrote: On 04/26/2017 04:34 PM, Jakub Jelinek wrote: Also, can't there be a way to shortcut all this processing if the charsets are the same? And is it a good idea if every pass that needs to do something with the

[PATCH,rs600] Add built-in function support for compare bytes instruction

This patch adds support for the compare bytes instruction, which has been available in the rs6000 architecture since Power6. The patch has been bootstrapped and tested on powerpc64le-unknown-linux and powerpc-unknown-linux (big-endian, with both -m32 and -m64 target options) with no regressions.

[PING] [PATCH] Force use of absolute path names for gcov

Ping... I attached a rebased patch file, with the doc changes and merge conflicts with trunk of today fixed, but otherwise identical. Thanks Bernd. On 04/21/17 22:26, Bernd Edlinger wrote: > > > On 04/21/17 21:50, Joseph Myers wrote: >> On Fri, 21 Apr 2017, Bernd Edlinger wrote: >> >>> So I

Re: [PATCH][ PR rtl-optimization/79286] Drop may_trap_p exception to testing dominance in update_equiv_regs

On 04/28/17 18:48, Jeff Law wrote: > On 04/23/2017 05:54 AM, Bernd Edlinger wrote: >> Hi Jeff, >> >> >> this patch tries to fix the handling of pic_offset_rtx + >> const(unspec(symbol_ref)+ const_int) in may_trap_p, >> and restores the original state of affairs in update_equiv_regs. >> >> >> What

Re: [PATCH 3/8] Simplify representation of locations of a block.

On 04/28/2017 12:28 PM, Martin Sebor wrote: Unless it's some other kind of vector, the patch adds a vector member to the class, which makes it not a PoD.(*) oh, well double ew. Your code is bad and you should feel bad. Write proper member initializers please. [*] Strictly speaking using

Re: [PATCH 4/7] [D] libiberty: Remove wrongly spec'd mangle rule for encoded integers.

On 04/25/2017 10:50 AM, Iain Buclaw wrote: On 20 April 2017 at 20:58, Iain Buclaw wrote: Hmm, it seems like D compilers until 3 years ago infact used to mangle in this way. Better keep it around then for a little while longer for compatibility. I'll follow-up with an

Re: [gcn][patch] Add -mgpu option and plumb in assembler/linker

On Fri, 28 Apr 2017, Andrew Stubbs wrote: > 3. Add -mgpu option and corresponding --with-gpu. I've deliberately used "gpu" > instead of "cpu" because I want offloading compilers to be able to say > "-mcpu=foo -foffload=-mgpu=bar", or even have the host compiler just > understand -mgpu and DTRT.

[gcn][patch] Add -mgpu option and plumb in assembler/linker

This patch, for the "gcn" branch, does three things: 1. Add specs to drive the LLVM assembler and linker. It requires them to be installed as "as" and "ld", under $target/bin, but then the compiler Just Works with these specs. 2. Switch to HSACO format version 2, and have the assembler

Re: [PATCH] Implement a warning for bogus sizeof(pointer) / sizeof(pointer[0])

On 04/28/17 17:29, Martin Sebor wrote: > On 04/28/2017 08:12 AM, Bernd Edlinger wrote: >> >> Do you want me to change the %qT format strings to %T ? > > Yes, with the surrounding %< and %> the nested directives should > use the unquoted forms, otherwise the printer would end up quoting > both the

Re: [PATCH][ PR rtl-optimization/79286] Drop may_trap_p exception to testing dominance in update_equiv_regs

On 04/23/2017 05:54 AM, Bernd Edlinger wrote: Hi Jeff, this patch tries to fix the handling of pic_offset_rtx + const(unspec(symbol_ref)+ const_int) in may_trap_p, and restores the original state of affairs in update_equiv_regs. What do you think is it OK to extract the symbol_ref out of the

Re: [PATCH] handle sprintf(d, "%s", ...) in gimple-ssa-sprintf.c

On 04/27/2017 07:35 PM, Martin Sebor wrote: On 04/25/2017 09:55 PM, Martin Sebor wrote: On 04/25/2017 04:05 PM, Jeff Law wrote: On 04/21/2017 03:33 PM, Martin Sebor wrote: I think I may have included the (partial) the fix for 79062 to get some tests to pass but I'm not 100% sure. The

Re: [PATCH] have -Wformat-overflow handle -fexec-charset (PR 80503)

On 04/28/2017 10:27 AM, Jakub Jelinek wrote: On Fri, Apr 28, 2017 at 10:22:29AM -0600, Jeff Law wrote: So the initialization could be done once per translation unit rather than once per function -- assuming the target character set doesn't change within a translation unit. That seems like it

Re: [PATCH] handle sprintf(d, "%s", ...) in gimple-ssa-sprintf.c

On 04/25/2017 09:55 PM, Martin Sebor wrote: On 04/25/2017 04:05 PM, Jeff Law wrote: On 04/21/2017 03:33 PM, Martin Sebor wrote: Bug 77671 - missing -Wformat-overflow warning on sprintf overflow with "%s", is caused by gimple-fold.c transforming s{,n}printf calls with a plain "%s" format string

Re: [PATCH 3/8] Simplify representation of locations of a block.

On 04/28/2017 05:47 AM, Nathan Sidwell wrote: On 04/21/2017 10:02 AM, marxin wrote: gcc/ChangeLog: 2017-04-26 Martin Liska * gcov.c (struct block_location_info): New struct. (process_file): Fill up the new structure. (read_graph_file): Replace usage of encoding

Re: [PATCH] have -Wformat-overflow handle -fexec-charset (PR 80503)

On Fri, Apr 28, 2017 at 10:22:29AM -0600, Jeff Law wrote: > So the initialization could be done once per translation unit rather than > once per function -- assuming the target character set doesn't change within > a translation unit. > > That seems like it ought to be easy. > > The table-lookup

Re: [PATCH] have -Wformat-overflow handle -fexec-charset (PR 80503)

On 04/27/2017 03:05 PM, Martin Sebor wrote: On 04/26/2017 04:34 PM, Jakub Jelinek wrote: Also, can't there be a way to shortcut all this processing if the charsets are the same? And is it a good idea if every pass that needs to do something with the exec charset chars caches its own results

Re: [testsuite] Add missing dg-require-effective-target alloca to gcc testsuite

On 04/27/2017 04:04 PM, Tom de Vries wrote: On 04/26/2017 01:57 PM, Jakub Jelinek wrote: I guess those should be decided case by case whether we want relative, absolute or saved line numbers. If the diagnostic is within the same function or code block as the stuff it is relative to, relative

Re: [PATCH] Implement a warning for bogus sizeof(pointer) / sizeof(pointer[0])

On 04/28/2017 08:12 AM, Bernd Edlinger wrote: On 04/28/17 00:52, Martin Sebor wrote: I suggest avoiding "element size" because the pointed-to argument need not be an array. Mentioning the types should help users better understand the problem (especially in C++ where types are often obscured by

New German PO file for 'gcc' (version 7.1-b20170427)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'gcc' has been submitted by the German team of translators. The file is available at: http://translationproject.org/latest/gcc/de.po (This file, 'gcc-7.1-b20170427.de.po',

[PATCH] x86: vpermil2p{s,d} have no commutative operands

While either of the last two operands can be in memory, they can't be swapped. gcc/ 2017-04-28 Jan Beulich * config/i386/sse.md (xop_vpermil23): Use alternatives. --- a/gcc/config/i386/sse.md +++ b/gcc/config/i386/sse.md @@ -17092,12 +17092,12 @@ (set_attr

Re: [PATCH] Destroy arguments for _Cilk_spawn calling in the child (PR 80038)

On 04/28/2017 08:31 AM, Xi Ruoyao wrote: On 2017-04-25 09:30 -0600, Jeff Law wrote: Given Richi's general agreement around the in_lto_p, let's go with the patch on the trunk only. Should I prepare (re-diff) a patch for current trunk? If you want for the trunk, yes. If you get positive

Re: [C++ Patch] PR 71577 ("[6/7/8 regression] ICE on invalid C++11 code (with extra struct initializer): in digest_init_r...")

On 04/28/2017 06:58 AM, Paolo Carlini wrote: Hi, now that 7.1.0 is almost out of the door, I'm sending a few simple patches which I have been testing for a while in my trees. This one is about an error recovery regression: I think it's correct to handle it by simply returning unconditionally

Re: [PATCH] Destroy arguments for _Cilk_spawn calling in the child (PR 80038)

On 2017-04-25 09:30 -0600, Jeff Law wrote: > Given Richi's general agreement around the in_lto_p, let's go with the  > patch on the trunk only. Should I prepare (re-diff) a patch for current trunk? > If you get positive feedback from Jan, then this can be backported to  > gcc-7 after it's been

Re: [PATCH] Implement a warning for bogus sizeof(pointer) / sizeof(pointer[0])

On 04/28/17 00:52, Martin Sebor wrote: >>> I suggest avoiding "element size" because the pointed-to argument >>> need not be an array. Mentioning the types should help users better >>> understand the problem (especially in C++ where types are often >>> obscured by layers of templates). It might

Re: [C++ Patch] Remove is_auto_or_concept, etc (Was: Re: [C++, concepts] Two slightly obscure pt.c functions?)

On 04/27/2017 02:02 PM, Paolo Carlini wrote: ... replying to myself, in practice we could do the below, which certainly passes testing, and in fact now seems to me even more obvious than I thought a couple of days ago... I'm insufficiently conceptified to know whether this is safe (but lack

[Ada] Fix remaining warnings in compiler bootstrap #3

This fixes some of the remaining warnings that appear in a compiler bootstrap. The above ones are false positives of -Wmaybe-uninitialized and some are fixed by initializing the variable in case the control flow is complicated; the rest is fixed by just adding pragma Warnings. No functional

[Ada] Info messages treated as errors with -gnatwe

This patch ensures that info messages are not treated as errors when warnings must be treated as errors due to -gnatwe. -- Source -- -- pack.ads package Pack is procedure Proc_1; procedure Proc_2; end Pack; -- pack.adb package body Pack is procedure Proc_1

[Ada] Deadlock when protected procedure propagates an exception

This patch fixes a bug where a protected procedure that propagates an exception can cause deadlock. This can happen if all of these checks are suppressed: Access_Check, Discriminant_Check, Range_Check, Index_Check, and Stack_Check (possibly by -gnatp), and the protected procedure calls something

[Ada] Fix remaining warnings in compiler bootstrap #2

This fixes some of the remaining warnings that appear in a compiler bootstrap. The above ones are false positives of -Wmaybe-uninitialized and most are fixed by initializing the variable in case the control flow is fairly complicated; a couple of very local cases are fixed by just adding pragma

[Ada] Freezing in expression function that is a completion.

The expresion in an expression function that is a completion freezes. This is implemented by first freezing the return type of the function, and then traversing the analyzed expression and freezing explicitly all type references within. If the expression includes a type conversion between access

[Ada] Fix some warnings in compiler bootstrap

This fixes some of the remaining warnings that appear in a compiler bootstrap. The above ones are false positives of -Wmaybe-uninitialized and most are fixed by initializing the variable in case the control flow is fairly complicated; a couple of very local cases are fixed by just adding pragma

Re: [PATCH] Fix PR80533

On Fri, 28 Apr 2017, Richard Biener wrote: > On Thu, 27 Apr 2017, Alexander Monakov wrote: > > > On Thu, 27 Apr 2017, Richard Biener wrote: > > > struct q { int n; long o[100]; }; > > > struct r { int n; long o[0]; }; > > > > > > union { > > > struct r r; > > > struct q q; > > > } u; >

Convert ipa-inline-analysis time interfaces to sreal

Hi, this is a second part of conversion which converts the interfaces form ipa-inline-analysis to inliner and ipa-cp. Again modulo the roundoff differences and compile time slowdown (caused by use of sreal) this patch should not have effect on code quality. Adjustments of time metrics will come

[PATCH] PR libstdc++/80553 don't allow destroying non-destructible types

We optimize _Destroy and _Destroy_n to do nothing when the type has a trivial destructor, which means we do nothing (instead of giving an error) when trying to destroy types with deleted destructors. Because deleted destructors are trivial. Because C++. This adds static assertions to reject

[PATCH] Remove superfluous "" in dg-error.

A tiny tweak to Tom's patch from yesterday. * testsuite/17_intro/headers/c++1998/stdc++_assert_neg.cc: Remove superfluous "" in dg-error. Committed to trunk. commit 5e7a406584889993b204ff640e3891ea5ca72a34 Author: Jonathan Wakely Date: Fri Apr 28 13:25:52

Re: [PATCH 5/8] Make gcno more precise about BBs really belonging to a line (PR gcov-profile/79891).

On 04/28/2017 01:41 PM, Nathan Sidwell wrote: > On 04/25/2017 09:08 AM, marxin wrote: >> gcc/ChangeLog: >> >> 2017-04-26 Martin Liska >> >> PR gcov-profile/79891 >> * gcov.c (add_line_counts): Assign BBs to lines just if the BB >> is marked by compiler as living on a

Re: Drop Z from X + Z < Y + Z

On Fri, Apr 28, 2017 at 02:25:55PM +0200, Richard Biener wrote: > On Fri, Apr 28, 2017 at 1:35 PM, Marc Glisse wrote: > > Hello, > > > > surprisingly, this did not cause any Wstrict-overflow failure. Some of it > > sounds more like reassoc's job, but it is convenient to

Re: Drop Z from X + Z < Y + Z

On Fri, Apr 28, 2017 at 1:35 PM, Marc Glisse wrote: > Hello, > > surprisingly, this did not cause any Wstrict-overflow failure. Some of it > sounds more like reassoc's job, but it is convenient to handle simple cases > in match.pd. I think we could wait until there are

[PATCH 2/2] Doxygen: transform ENUM_BITFIELD and comments starting with '/**'.

Hi. As mentioned in the subject, another 2 transformations. With David's patch applied and my 2 hunks, I can see just these 3 warnings related to verbatim/end verbatim decoration: /home/marxin/Programming/gcc/gcc/gcov-io.c:464: warning: unexpected command endverbatim

[PATCH 1/2] Change comment style to one we normally use.

Hi. First follow-up patch changes comment style in couple of locations so that filter_params.py can transform them to Doxygen style. I verified that there's no compilation error caused by the patch. Ready for trunk, Martin >From 3867980352bd1a666395470c5ff138d1d545b311 Mon Sep 17 00:00:00 2001

Re: [PATCH 1/2] Port Doxygen support script from Perl to Python; add unittests

On 03/17/2017 02:51 AM, David Malcolm wrote: Hello. I've just tested you patches and I can confirm that they work :) I've got couple of related questions: > It's possible to run GCC's sources through Doxygen by setting > INPUT_FILTER = contrib/filter_gcc_for_doxygen > within

New template for 'gcc' made available

Hello, gentle maintainer. This is a message from the Translation Project robot. (If you have any questions, send them to .) A new POT file for textual domain 'gcc' has been made available to the language teams for translation. It is archived as:

Re: [PATCH 0/8] GCOV improvements

On 04/28/2017 01:49 PM, Nathan Sidwell wrote: > On 04/28/2017 05:26 AM, marxin wrote: >> Hi. >> >> Following patch series improves the infrastructure, fixes couple of issues >> and hopefully improves also documentation of the functionality. >> I decided to split the changes into various patches to

Re: [PATCH 0/8] GCOV improvements

On 04/28/2017 05:26 AM, marxin wrote: Hi. Following patch series improves the infrastructure, fixes couple of issues and hopefully improves also documentation of the functionality. I decided to split the changes into various patches to make it easier for reviewers. thanks for doing this. I

Re: [PATCH 2/8] Remove .gcno file when compilation does not success (PR driver/56469).

On 04/19/2017 03:56 AM, marxin wrote: gcc/ChangeLog: 2017-04-19 Martin Liska PR driver/56469 * coverage.c (coverage_remove_note_file): New function. * coverage.h: Declare the function. * toplev.c (finalize): Clean if an error has been seen.

Re: [PATCH 3/8] Simplify representation of locations of a block.

On 04/21/2017 10:02 AM, marxin wrote: gcc/ChangeLog: 2017-04-26 Martin Liska * gcov.c (struct block_location_info): New struct. (process_file): Fill up the new structure. (read_graph_file): Replace usage of encoding by the newly added struct.

Re: Make pretty printers version namespace dependant

On 28/04/17 12:38 +0100, Jonathan Wakely wrote: On 28/04/17 09:41 +0100, Jonathan Wakely wrote: On 27/04/17 21:27 +0200, François Dumont wrote: Oh, I thought it was obviously better to not register useless Printers. But if you need a bug report or an explicit test showing that it is better

Re: [PATCH 1/8] gcno file: do not stream block flags (PR gcov-profile/80031).

On 04/21/2017 08:40 AM, marxin wrote: gcc/ChangeLog: 2017-03-13 Martin Liska PR gcov-profile/80031 * gcov-dump.c (tag_blocks): Just print number of basic blocks. * gcov-io.h (GCOV_TAG_BLOCKS_NUM): Remove unused macro. * gcov.c

Re: [PATCH 5/8] Make gcno more precise about BBs really belonging to a line (PR gcov-profile/79891).

On 04/25/2017 09:08 AM, marxin wrote: gcc/ChangeLog: 2017-04-26 Martin Liska PR gcov-profile/79891 * gcov.c (add_line_counts): Assign BBs to lines just if the BB is marked by compiler as living on a line. (get_cycles_count): Remove usage of

Re: Make pretty printers version namespace dependant

On 28/04/17 09:41 +0100, Jonathan Wakely wrote: On 27/04/17 21:27 +0200, François Dumont wrote: Oh, I thought it was obviously better to not register useless Printers. But if you need a bug report or an explicit test showing that it is better then I don't have it. Maybe a gdb guy could tell

Drop Z from X + Z < Y + Z

Hello, surprisingly, this did not cause any Wstrict-overflow failure. Some of it sounds more like reassoc's job, but it is convenient to handle simple cases in match.pd. I think we could wait until there are reports of regressions related to register pressure before adding single_use tests.

Re: [PATCH 4/8] Introduce new option -w which shows verbose informations.

On 04/25/2017 08:05 AM, marxin wrote: gcc/ChangeLog: 2017-04-26 Martin Liska * gcov.c (process_args): Handle new argument 'w'. (read_graph_file): Assign ID to BBs. (output_branch_count): Display BB # if verbose flag is set. (output_lines):

Re: [PATCH 6/8] Fix format_gcov to not print misleading values (PR gcov-profile/53915)

On 04/27/2017 06:04 AM, marxin wrote: gcc/ChangeLog: 2017-04-27 Martin Liska PR gcov-profile/53915 * gcov.c (format_gcov): Print 'NAN %' when top > bottom. ok -- Nathan Sidwell

Re: [PATCH 8/8] Enhance documentation of gcov.

On 04/27/2017 05:24 AM, marxin wrote: gcc/ChangeLog: 2017-04-27 Martin Liska * doc/gcov.texi: Enhance documentation of gcov. ok -- Nathan Sidwell

Re: [PATCH 7/8] Sort options of gcov, gcov-dump and gcov-tool both in --help and documentation

On 04/27/2017 05:02 AM, marxin wrote: gcc/ChangeLog: 2017-04-27 Martin Liska * doc/gcov.texi: Sort options in alphabetic order. * doc/gcov-dump.texi: Likewise. * doc/gcov-tool.texi: Likewise. * gcov.c (print_usage): Likewise. *

[C++ Patch] PR 71577 ("[6/7/8 regression] ICE on invalid C++11 code (with extra struct initializer): in digest_init_r...")

Hi, now that 7.1.0 is almost out of the door, I'm sending a few simple patches which I have been testing for a while in my trees. This one is about an error recovery regression: I think it's correct to handle it by simply returning unconditionally error_mark_node upon "too many initializers"

[PATCH 8/8] Enhance documentation of gcov.

gcc/ChangeLog: 2017-04-27 Martin Liska * doc/gcov.texi: Enhance documentation of gcov. --- gcc/doc/gcov.texi | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/gcc/doc/gcov.texi b/gcc/doc/gcov.texi index 1befb5a3e08..c96f86df830 100644 ---

[PATCH 4/8] Introduce new option -w which shows verbose informations.

gcc/ChangeLog: 2017-04-26 Martin Liska * gcov.c (process_args): Handle new argument 'w'. (read_graph_file): Assign ID to BBs. (output_branch_count): Display BB # if verbose flag is set. (output_lines): Likewise for arcs. (print_usage):

[PATCH 7/8] Sort options of gcov, gcov-dump and gcov-tool both in --help and documentation

gcc/ChangeLog: 2017-04-27 Martin Liska * doc/gcov.texi: Sort options in alphabetic order. * doc/gcov-dump.texi: Likewise. * doc/gcov-tool.texi: Likewise. * gcov.c (print_usage): Likewise. * gcov-dump.c (print_usage): Likewise. *

[PATCH 5/8] Make gcno more precise about BBs really belonging to a line (PR gcov-profile/79891).

gcc/ChangeLog: 2017-04-26 Martin Liska PR gcov-profile/79891 * gcov.c (add_line_counts): Assign BBs to lines just if the BB is marked by compiler as living on a line. (get_cycles_count): Remove usage of the union.

[PATCH 6/8] Fix format_gcov to not print misleading values (PR gcov-profile/53915)

gcc/ChangeLog: 2017-04-27 Martin Liska PR gcov-profile/53915 * gcov.c (format_gcov): Print 'NAN %' when top > bottom. --- gcc/gcov.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/gcc/gcov.c b/gcc/gcov.c index 0adb4466f70..22378583c5c 100644 ---

[PATCH 1/8] gcno file: do not stream block flags (PR gcov-profile/80031).

gcc/ChangeLog: 2017-03-13 Martin Liska PR gcov-profile/80031 * gcov-dump.c (tag_blocks): Just print number of basic blocks. * gcov-io.h (GCOV_TAG_BLOCKS_NUM): Remove unused macro. * gcov.c (read_graph_file): Read just number of blocks. *

[PATCH 3/8] Simplify representation of locations of a block.

gcc/ChangeLog: 2017-04-26 Martin Liska * gcov.c (struct block_location_info): New struct. (process_file): Fill up the new structure. (read_graph_file): Replace usage of encoding by the newly added struct. (add_line_counts): Likewise.

[PATCH 0/8] GCOV improvements

Hi. Following patch series improves the infrastructure, fixes couple of issues and hopefully improves also documentation of the functionality. I decided to split the changes into various patches to make it easier for reviewers. Bootstraps and survives regression tests on ppc64le-linux-gnu and

[PATCH 2/8] Remove .gcno file when compilation does not success (PR driver/56469).

gcc/ChangeLog: 2017-04-19 Martin Liska PR driver/56469 * coverage.c (coverage_remove_note_file): New function. * coverage.h: Declare the function. * toplev.c (finalize): Clean if an error has been seen. --- gcc/coverage.c | 12

RE: [PATCH] Match x86 family machine constraints section with constarints.md

Hi, Thank you for your comments. I edited my patch accordingly. As for some of your doubts: - REX is the opcode prefix to access 64-bit register extensions introduced in IA-32e mode. - EVEX is the encoding prefix which applies to SIMD operating instructions operating on XMM, YMM and ZMM

Re: [PATCH] Improve VRP range intersection for partly symbolic ranges

On Thu, 27 Apr 2017, Richard Biener wrote: > On April 27, 2017 4:06:48 PM GMT+02:00, "Bin.Cheng" > wrote: > >On Thu, Apr 27, 2017 at 2:49 PM, Richard Biener > >wrote: > >> > >> The following makes intersecting [-INF, +10] and [a + -1, +INF] > >> to

Re: [PATCH] Fix AIX bootstrap comparison due to empty *-tests.c and selftest* files (PR bootstrap/80531)

On Fri, 28 Apr 2017, Jakub Jelinek wrote: > On Fri, Apr 28, 2017 at 07:56:23AM +0200, Richard Biener wrote: > > On April 27, 2017 10:20:57 PM GMT+02:00, Jakub Jelinek > > wrote: > > >This is something that fails bootstrap newly in GCC 7 and only with > > >(now on the branch

Re: [PATCH] Fix AIX bootstrap comparison due to empty *-tests.c and selftest* files (PR bootstrap/80531)

On Fri, Apr 28, 2017 at 07:56:23AM +0200, Richard Biener wrote: > On April 27, 2017 10:20:57 PM GMT+02:00, Jakub Jelinek > wrote: > >This is something that fails bootstrap newly in GCC 7 and only with > >(now on the branch default --enable-checking=release (or >

[PATCH] Bump LTO_major

Committed. Richard. 2017-04-28 Richard Biener * lto-streamer.h (LTO_major_version): Bump to 7. Index: gcc/lto-streamer.h === --- gcc/lto-streamer.h (revision 247362) +++ gcc/lto-streamer.h (working

  1   2   >