Re: [PATCH][AArch64] Implement ALU_BRANCH fusion

Hi James, >> My reason for asking is that the instruction fusion implemented in LLVM >> ( lib/Target/AArch64/AArch64MacroFusion.cpp::shouldScheduleAdjacent ) Sorry. There seems to be some confusion in the branch instructions. The branch should be conditional for ALU_BRANCH fusion. Please find

[P1][bootstrap/79771] [PATCH] Hack around zlib bug on Cygwin

Our current version of zlib has a bug where zlib has an unsatisfied reference to _wopen on Cygnwin. This is a bug in the upstream zlib and is being discussed there. This patch (from Yaakov Selkowitz) works around the problem and we'll carry it as a local change until upstream decides on

Re: [PATCH] correct handling of negative-positive precision ranges with floating directives (PR 79800)

On 03/13/2017 06:33 PM, Martin Sebor wrote: The output of a floating point directive whose precision is specified by an asterisk with an argument that's in a range that includes both negative and positive values less than six may include between zero and six fractional digits plus a decimal

Re: [PATCH] Suppress compiler warning in libgcc/unwind-seh.c

On 03/01/2017 04:36 AM, JonY wrote: Patch OK? ChangeLog: * unwind-seh.c: Suppress warnings for RtlUnwindEx() calls. You know this stuff better than anyone else working with GCC. If you think this is the right thing to do for the SEH code, go for it. jeff

Re: patch, libfortran] [patch, fortran] Fix PR 79956, part two, attempt 3

On 03/14/2017 04:01 PM, Thomas Koenig wrote: > Hello world, > > well, here is the third attempt at fixing the second part of the PR. > Glancing over the source, I think there are quite a few places where > we currently issue a runtime error which we could replace by an > assert, but that's

Re: [PATCH doc] use "cannot" consistently

On 03/14/2017 02:53 PM, Richard Kenner wrote: The GCC manual uses "cannot" in most places (280 lines) but there are a few instances of "can't" (33 lines). The attached patch replaces the informal "can't" with the former for consistency. In my opinion, this is the wrong direction.

[PATCH] Fix location of sizeof/alignof (PR c++/80016)

PR c++/80016 reports an issue with bizarre underlined range for a complicated expression. The root cause for the incorrect *starting* location of that range is that alignof and sizeof expressions currently have start == finish == caret at the opening parenthesis of the expression. This patch

[PATCH] Fix location of typeid() (PR c++/80014)

PR c++/80014 reports an issue where no caret is printed when issuing an error for this bogus code: !typeid(void); Root cause is that we're not setting up the location for the cp_expr for the typeid expression, so that !typeid(void) has start == caret at the '!', but finish ==

[PATCH] omp-offload.c: translation fixes (PR translation/80001)

Successfully bootstrapped on x86_64-pc-linux-gnu. OK for trunk? (either now in stage 4, or for next stage1?) gcc/ChangeLog: PR translation/80001 * omp-offload.c (oacc_loop_fixed_partitions): Make diagnostics more amenable to translation.

Re: [PATCH 1/5] Fix *_CST ICEs connected to MPX.

2017-03-13 16:33 GMT+03:00 Martin Liška : > On 03/13/2017 02:07 PM, Richard Biener wrote: >> No, that can't happen. I said that for example for >> >> struct S { ... } s; >> foo (s); >> >> pass_by_reference may be true but on gimple you see a struct s as >> actual argument. I'm

Re: [PATCH,RS6000] PR79963: Correct which condition code bit represents result of vec_any_eq built-in function

Hi Kelvin, On Tue, Mar 14, 2017 at 03:06:13PM -0600, Kelvin Nilsen wrote: > 2017-03-14 Kelvin Nilsen > > PR target/79963 > * config/rs6000/altivec.h (vec_all_ne): Under __cplusplus++ and It is spelled __cplusplus__. > __POWER9_VECTOR__ #ifdef control,

Re: Reload fix for an old aarch64 issue

On 03/14/2017 05:22 PM, Bernd Schmidt wrote: This triggered a kernel miscompilation with an old (4.8 I think) aarch64 toolchain. Here's the reloads for the insn where things go wrong: Reloads for insn # 210 Reload 0: reload_in (DI) = (reg/v/f:DI 80 [ pgdata ]) GENERAL_REGS,

Re: Reload fix for an old aarch64 issue

On Tue, Mar 14, 2017 at 4:22 PM, Bernd Schmidt wrote: > This triggered a kernel miscompilation with an old (4.8 I think) aarch64 > toolchain. Yes RHEL's 4.8 has the issue. So did Cavium/MontaVista's GCC 4.7 with AARCH64 support backported to it. We would work around the

Reload fix for an old aarch64 issue

This triggered a kernel miscompilation with an old (4.8 I think) aarch64 toolchain. Here's the reloads for the insn where things go wrong: Reloads for insn # 210 Reload 0: reload_in (DI) = (reg/v/f:DI 80 [ pgdata ]) GENERAL_REGS, RELOAD_FOR_INPUT_ADDRESS (opnum = 0)

Re: [PATCH] PR libstdc++/79789 fix non-reserved names in headers

On 10/03/17 15:20 +, Jonathan Wakely wrote: On 09/03/17 19:46 +, Jonathan Wakely wrote: On 03/03/17 10:47 -0500, David Edelsohn wrote: This patch caused a new regression on AIX. I'm unable to bootstrap on either gcc111 or gcc119 so I can't test the fix. export

Re: Combiner fix for PR79910

On 03/15/2017 12:03 AM, Jeff Law wrote: On 03/10/2017 04:24 PM, Bernd Schmidt wrote: PR rtl-optimization/79910 * combine.c (record_used_regs): New static function. (try_combine): Handle situations where there is an additional instruction between I2 and I3 which needs to have a

Re: Combiner fix for PR79910

On 03/10/2017 04:24 PM, Bernd Schmidt wrote: In this PR, we have a few insns involved in two instruction combinations: insn 16: set r100 insn 27: some calculation insn 28: some calculation insn 32: using r100 insn 33: using r100 insn 35: some calculation Then we combine insns 27, 28 and 33,

patch, libfortran] [patch, fortran] Fix PR 79956, part two, attempt 3

Hello world, well, here is the third attempt at fixing the second part of the PR. Glancing over the source, I think there are quite a few places where we currently issue a runtime error which we could replace by an assert, but that's something for 8.0. Regression-tested on x86_64-pc-linux-gnu.

Re: [patch, fortran] PR39239 Warning about EQUIVALENCE and VOLATILE

On 03/14/2017 10:42 PM, Jerry DeLisle wrote: On 03/14/2017 01:17 PM, Nicolas Koenig wrote: Hello everyone, a simple patch to throw a warning if not all and not none of the equivalence objects are volatile. (And the according modification of gfortran.dg/volatile11.f90) Nicolas Regression

Re: [PATCH doc] use "cannot" consistently

On Tue, 14 Mar 2017, Martin Sebor wrote: > PS I wasted quite a bit of time updating tm.texi. I kept getting > the error below and didn't realize (forgot) that it was asking me > to copy $objdir/gcc/tm.texi to $srcdir/gcc/doc/tm.texi. Can > someone explain why this file requires these special

Re: [PATCH doc] use "cannot" consistently

On 03/14/2017 01:41 PM, Richard Sandiford wrote: Martin Sebor writes: @@ -373,7 +373,7 @@ example, this code would produce an error: @smallexample #if 0 -You can't expect this to work. +You cannot expect this to work. #endif @end smallexample Sure the maintainers

[gomp4] cleanup trans-stmt.h

I noticed that gcc/fortran/trans-stmt.h made a reference to a non-existent trans-openacc.c. Those functions have been placed in trans-openmp.c. This patch has been applied to gomp-4_0-branch to correct that error. Cesar 2017-03-14 Cesar Philippidis gcc/fortran/ *

Re: [PATCH] MPX: fix PR middle-end/79753

2017-03-10 16:15 GMT+03:00 Martin Liška : > Hello. > > Currently, __builtin_ia32_bndret is used for all functions that have non-void > return type. I think the right fix is to return bounds just for a bounded > type. > > Patch can bootstrap on x86_64-linux-gnu and survives

Re: [PATCH], PR target/79947, Fix compiler segmentation fault with -Ofast -mno-powerpc-gfxopt

Hi Mike, On Tue, Mar 14, 2017 at 05:01:53PM -0400, Michael Meissner wrote: > In PR target/79947, the code for using the float reciprocal square root > estimate instruction did not check if the -mpowerpc-gfxopt option was enabled. > The code needs this option to generate a conditional floating

Re: [PATCH] add calls.c to GTFILES in Makefile.in

On 03/07/2017 06:03 PM, Martin Sebor wrote: In bug 79936 - ICE with -Walloc-size-larger-than=32767 the reporter encountered an ICE on x86_64-apple-darwin10.8.0 caused by GCC source file that implements the warning accessing a global tree without having included the file in GTFILES make variable.

Re: [PATCH] correct aligned_alloc argument order (PR 80020)

On 03/13/2017 02:44 AM, Richard Biener wrote: On Mon, Mar 13, 2017 at 2:13 AM, Martin Sebor wrote: r243470 decorates standard allocation functions like alloca and malloc with attribute alloc_size. However, in applying the attribute to aligned_alloc I had overlooked that the

Re: [patch, fortran] PR39239 Warning about EQUIVALENCE and VOLATILE

On 03/14/2017 01:17 PM, Nicolas Koenig wrote: > Hello everyone, > > a simple patch to throw a warning if not all and not none of the equivalence > objects are volatile. (And the according modification of > gfortran.dg/volatile11.f90) > > Nicolas > > Regression tested for: > > GNU Fortran (GCC)

Re: [PATCH] Fix PR79908

> On Mar 14, 2017, at 11:07 AM, Bill Schmidt > wrote: >> >> Your suggestion failed bootstrap in libiberty on vprintf-support.c. >> Compilation failed with: >> >> /home/wschmidt/gcc/build/gcc-mainline-test2-debug/gcc/xgcc >>

[PATCH,RS6000] PR79963: Correct which condition code bit represents result of vec_any_eq built-in function

This patch corrects several errors in a patch that was submitted on 2017-03-01. A copy-and-paste error in the previous patch resulted in accidental use of the lt flag instead of the eq flag to represent the outcome of the vec_any_eq built-in function. Also, in reviewing the code of the previous

[PATCH], PR target/79947, Fix compiler segmentation fault with -Ofast -mno-powerpc-gfxopt

In PR target/79947, the code for using the float reciprocal square root estimate instruction did not check if the -mpowerpc-gfxopt option was enabled. The code needs this option to generate a conditional floating point move. I have checked this patch on the trunk, and it fixes the problem and it

Re: [PATCH doc] use "cannot" consistently

> The GCC manual uses "cannot" in most places (280 lines) but there > are a few instances of "can't" (33 lines). > > The attached patch replaces the informal "can't" with the former > for consistency. In my opinion, this is the wrong direction. Contractions are becoming more acceptable in even

Re: [PATCH] Windows support for std::filesystem

niXman 2017-02-12 20:28: Hi, Tested on i686/x86_64-MinGW-W64 Please test possible regressions on posix platform. As continuation for: https://gcc.gnu.org/ml/libstdc++/2017-02/msg00041.html Regression on posix platform was fixed. Tested on i686/x86_64-MinGW-W64 and x86_64-linux-gnu.

[wwwdocs] remove power.org links from readings.html

Segher confirmed that power.org is gone and that it's okay to remove those links for now. He kindly agreed to help and look for alternatives. Applied. Gerald Index: readings.html === RCS file:

[patch, fortran] PR39239 Warning about EQUIVALENCE and VOLATILE

Hello everyone, a simple patch to throw a warning if not all and not none of the equivalence objects are volatile. (And the according modification of gfortran.dg/volatile11.f90) Nicolas Regression tested for: GNU Fortran (GCC) 7.0.1 20170311 (experimental) Changelog: 2017-03-13 Nicolas

Re: [wwwdocs] Document in changes.html -fcode-hoisting, -fipa-bit-cp, -fipa-vrp, -fsplit-loops, GCJ removal, x86 ISA additions, -fshrink-wrap-separate etc.

On 03/12/2017 05:23 PM, Gerald Pfeifer wrote: Hi Martin, On Mon, 27 Feb 2017, Martin Sebor wrote: Sorry to be jumping in so late. I only noticed this bit now. I would suggest to say that these new built-ins evaluate to integer constant expressions when their arguments do. Not all C

Re: [PATCH doc] use "cannot" consistently

Martin Sebor writes: > @@ -373,7 +373,7 @@ example, this code would produce an error: > > @smallexample > #if 0 > -You can't expect this to work. > +You cannot expect this to work. > #endif > @end smallexample > Sure the maintainers would have caught this, but: the "'"

Re: [PATCH 1/5] testsuite: attr-alloc_size-11.c (PR79356)

On 03/12/2017 07:32 PM, Martin Sebor wrote: On 03/10/2017 10:51 PM, Jeff Law wrote: On 03/10/2017 09:20 AM, Martin Sebor wrote: On 03/10/2017 05:57 AM, Rainer Orth wrote: Hi Segher, On Fri, Feb 10, 2017 at 11:56:39AM +0100, Rainer Orth wrote: Segher Boessenkool

[PATCH doc] use "cannot" consistently

In formal writing it's recommended to prefer the word "cannot" to the somewhat informal "can't." The GCC manual uses "cannot" in most places (280 lines) but there are a few instances of "can't" (33 lines). The attached patch replaces the informal "can't" with the former for consistency. Thanks

Re: [PATCH] Various fixes for facets

On 13/03/17 19:35 +, Jonathan Wakely wrote: This is a series of patches to fix various bugs in the Unicode character conversion facets. Ther first patch fixes a silly < versus <= bug that meant that 0x got written as a surrogate pair instead of as simply 0xff, and an endianness bug for

Re: C++ PATCH to fix ICE in replace_placeholders_r (PR c++/79937)

On Tue, Mar 14, 2017 at 2:33 PM, Jason Merrill wrote: > On Tue, Mar 7, 2017 at 12:10 PM, Marek Polacek wrote: >> In this testcase we have >> C c = bar (X{1}); >> which store_init_value sees as >> c = TARGET_EXPR >

Re: C++ PATCH to fix ICE in replace_placeholders_r (PR c++/79937)

On Tue, Mar 7, 2017 at 12:10 PM, Marek Polacek wrote: > In this testcase we have > C c = bar (X{1}); > which store_init_value sees as > c = TARGET_EXPR .n=(&)->i}>)> > i.e. we're initializing "c" with a TARGET_EXPR. We call

Re: Fix IRA issue, PR79728

On 03/03/2017 06:51 AM, Bernd Schmidt wrote: This is an ICE where setup_pressure_classes fails if xmm0 is a global reg. Instead of GENERAL/FLOAT/SSE/MMX_REGS, it computes only SSE_FIRST_REG as the third register class. The problem is that the costs for moving between SSE_FIRST_REG and SSE_REGS

Re: [PATCH][PR sanitizer/77631] Support separate debug info in libbacktrace

Thanks for answer, i got it now. I will also delete all readlink code. Looks like is no reason to use it instead just one call of realpath(char*,char*). Binutils using realpath in the same cases. On 03/14/2017 07:26 PM, Ian Lance Taylor wrote: On Tue, Mar 14, 2017 at 7:30 AM, Denis Khalikov

Re: Fix IRA issue, PR79728

On 03/03/2017 06:51 AM, Bernd Schmidt wrote: This is an ICE where setup_pressure_classes fails if xmm0 is a global reg. Instead of GENERAL/FLOAT/SSE/MMX_REGS, it computes only SSE_FIRST_REG as the third register class. The problem is that the costs for moving between SSE_FIRST_REG and SSE_REGS

Re: [PATCH] Use fixed_nonglobal_reg_set to deduce ok_regs (PR rtl-optimization/79728)

On 03/06/2017 01:27 AM, Xi Ruoyao wrote: Hi, After Bernd fixed PR44281 (r235809), the registers fixed only because they are global can be selected by IRA. However, since they are not in ok_regs, the move cost estimation about them are wrong. Then an assertion in ira.c failed and then ICE. To

Re: [PATCH] Install gcov-dump.

On 14.03.2017 15:15, Richard Biener wrote: > On Tue, Mar 14, 2017 at 1:30 PM, Martin Liška wrote: >> Tested on my local machine that's properly installed. >> >> Ready for trunk? > > Ok. > > Richard. shouldn't that go to the active branches as well? Matthias

Re: terminology: zero character vs. null character

On 03/13/2017 04:34 PM, Bruce Korb wrote: On 03/13/17 15:02, Gerald Pfeifer wrote: On Mon, 13 Mar 2017, Joseph Myers wrote: I am currently translating GCC into German. During that, I noticed that in some places the term "zero character" means '\0'. The official term though is "null character",

Re: [PATCH][PR sanitizer/77631] Support separate debug info in libbacktrace

On Tue, Mar 14, 2017 at 7:30 AM, Denis Khalikov wrote: > Thanks for review, got all of my mistakes, except one. > > >> - descriptor = backtrace_open (info->dlpi_name, pd->error_callback, >> - pd->data, _not_exist); >> + descriptor >> + =

C++ backports to 6

I've backported the attached patches gcc-6. Marek Bootstrapped/regtested on x86_64-linux, ok for trunk? 2017-03-14 Marek Polacek PR c++/79962 PR c++/79984 * c-common.c (handle_nonnull_attribute): Save the result of default

Re: [PATCH] Fix PR79908

On Mar 14, 2017, at 9:32 AM, Bill Schmidt wrote: > >> On Mar 14, 2017, at 9:25 AM, Richard Biener >> wrote: >> > Better is sth like > > Index: gcc/tree-stdarg.c >

Re: [C++ PATCH] 79393 fix

On Tue, Mar 14, 2017 at 10:43 AM, Nathan Sidwell wrote: > On 03/13/2017 06:20 PM, Nathan Sidwell wrote: >> >> On 03/13/2017 05:05 PM, Jason Merrill wrote: >> >>> It looks like you're ignoring the access for all base destructors; >>> handling this in synthesized_method_base_walk

Re: [PATCH] add calls.c to GTFILES in Makefile.in (PR 79936)

On 03/14/2017 03:01 AM, Richard Biener wrote: On Tue, Mar 14, 2017 at 1:37 AM, Martin Sebor wrote: Ping: this a P3 regression targeted at 7.0.1. It was found on x86_64-apple-darwin10.8.0 but affects all targets (even if it doesn't happen to manifest on them):

Re: [PATCH][DOC] Document -Wchkp (PR middle-end/79831).

On 03/14/2017 09:01 AM, Martin Liška wrote: Hello. This is small documentation patch that lists and briefly describes -Wchkp. OK. jeff

Re: [PATCH][DOC] Document options that can't be combined with -fcheck-pointer-bounds.

On 03/14/2017 09:02 AM, Martin Liška wrote: Hello. This mentions all options that can't be combined with -fcheck-pointer-bounds. OK. jeff

[PATCH][DOC] Document options that can't be combined with -fcheck-pointer-bounds.

Hello. This mentions all options that can't be combined with -fcheck-pointer-bounds. Thanks, Martin >From 78e199c5f0359de1c74cf44aaa8947a0ae950dd3 Mon Sep 17 00:00:00 2001 From: marxin Date: Tue, 14 Mar 2017 16:00:03 +0100 Subject: [PATCH] Document options that can't be combined

[PATCH][DOC] Document -Wchkp (PR middle-end/79831).

Hello. This is small documentation patch that lists and briefly describes -Wchkp. Martin >From 553e0c83a1b1efbaff7666f5ab7303e816b958d4 Mon Sep 17 00:00:00 2001 From: marxin Date: Tue, 14 Mar 2017 15:41:47 +0100 Subject: [PATCH] Document -Wchkp (PR middle-end/79831).

[PATCH] PR libstdc++/79162 disambiguate assignment from string_view

This fixes a new ambiguity in C++17 mode introduced by string_view support in basic_string. PR libstdc++/79162 * include/bits/basic_string.h [_GLIBCXX_USE_CXX11_ABI] (basic_string::operator=(basic_string_view)): Replace with a constrained template.

[PATCH][PR target/79752] fix rs6000 power9 peephole2 for udiv/umod -- backported to gcc-6-branch

This showed up in power9 code for __divkf3 software float support and caused a divd to be emitted where we needed a divdu. backported/bootstrapped/regtested to gcc-6-branch Index: gcc/config/rs6000/rs6000.md === ---

Re: [C++ PATCH] 79393 fix

On 03/13/2017 06:20 PM, Nathan Sidwell wrote: On 03/13/2017 05:05 PM, Jason Merrill wrote: It looks like you're ignoring the access for all base destructors; handling this in synthesized_method_base_walk would let you limit the change to vbases with virtual destructors. That function also

Re: [PATCH] Fix PR79908

> On Mar 14, 2017, at 9:25 AM, Richard Biener > wrote: > > On Tue, Mar 14, 2017 at 3:20 PM, Bill Schmidt > wrote: >> >>> On Mar 14, 2017, at 7:50 AM, Bill Schmidt >>> wrote: >>> >>> On Mar 14,

Re: [PATCH][PR sanitizer/77631] Support separate debug info in libbacktrace

Thanks for review, got all of my mistakes, except one. > - descriptor = backtrace_open (info->dlpi_name, pd->error_callback, > - pd->data, _not_exist); > + descriptor > + = backtrace_open_debugfile (info->dlpi_name, pd->error_callback, pd->data, > +_does_not_exist, pd->state,

Re: [PATCH] Fix PR79908

On Tue, Mar 14, 2017 at 3:20 PM, Bill Schmidt wrote: > >> On Mar 14, 2017, at 7:50 AM, Bill Schmidt >> wrote: >> >> >>> On Mar 14, 2017, at 3:57 AM, Richard Biener >>> wrote: >>> >>> On Tue, Mar 14, 2017 at

Re: [PATCH] Fix PR79908

> On Mar 14, 2017, at 7:50 AM, Bill Schmidt wrote: > > >> On Mar 14, 2017, at 3:57 AM, Richard Biener >> wrote: >> >> On Tue, Mar 14, 2017 at 1:04 AM, Bill Schmidt >> wrote: >>> >>> Index:

Re: [PATCH] Install gcov-dump.

On Tue, Mar 14, 2017 at 1:30 PM, Martin Liška wrote: > Tested on my local machine that's properly installed. > > Ready for trunk? Ok. Richard. > Thanks, > Martin

Re: [PATCH] gcov: Mark BBs that do not correspond to a line in source code (PR gcov-profile/79891).

On Tue, 14 Mar 2017, Martin Liška wrote: > On 03/14/2017 11:48 AM, Richard Biener wrote: > > On Tue, 14 Mar 2017, Martin Liška wrote: > > > >> On 03/14/2017 11:30 AM, Richard Biener wrote: > >>> On Tue, 14 Mar 2017, Martin Liška wrote: > >>> > On 03/14/2017 11:13 AM, Richard Biener wrote: >

Re: [PATCH] gcov: Mark BBs that do not correspond to a line in source code (PR gcov-profile/79891).

On 03/14/2017 11:48 AM, Richard Biener wrote: > On Tue, 14 Mar 2017, Martin Liška wrote: > >> On 03/14/2017 11:30 AM, Richard Biener wrote: >>> On Tue, 14 Mar 2017, Martin Liška wrote: >>> On 03/14/2017 11:13 AM, Richard Biener wrote: > On Tue, 14 Mar 2017, Martin Liška wrote: >

Re: [doc] Omit up pointer (DIR) in gcc.texi and gccint.texi?

On Mon, 13 Mar 2017, Joseph Myers wrote: > I think that as far as possible we should just use "@node node-name" > without any of the subsequent arguments pointing to other nodes. Thanks, Joseph. I went ahead and applied the patch below. Gerald 2017-03-13 Gerald Pfeifer

Re: [PATCH][ARM] PR target/71436: Restrict *load_multiple pattern till after LRA

On 07/02/17 14:49, Kyrill Tkachov wrote: On 18/01/17 09:49, Kyrill Tkachov wrote: On 19/12/16 14:53, Jakub Jelinek wrote: On Thu, Dec 15, 2016 at 10:00:14AM +, Richard Earnshaw (lists) wrote: sorry, pasted the wrong bit of code. That should read when we generate: (insn 55 19 67 3

Re: [PATCH][PR sanitizer/77631] Support separate debug info in libbacktrace

On Mon, Mar 13, 2017 at 10:16 AM, Denis Khalikov wrote: > Hello everyone, i have a patch for this issue. > > List of implemented functionality: > > 1.Reading .gnu_debuglink section from ELF file: > a. Reading name of debug info file. > b. Verifying crc32 sum. > >

Re: [PATCH 4/N] Do not ICE on an invalid input for MV.

On Tue, Mar 14, 2017 at 1:24 PM, Martin Liška wrote: > On 03/14/2017 12:09 PM, Richard Biener wrote: >> On Tue, Mar 14, 2017 at 11:24 AM, Martin Liška wrote: >>> Hello. >>> >>> This fixes ICE when one does not provide valid target names: >>>

Re: [PATCH][PR sanitizer/77631] Support separate debug info in libbacktrace

Ok, thanks, i will change patch to use crc32 from libiberty and also implement searching for debuginfo with build id. As it was implemented to binutils PR binutils/20876. On 03/14/2017 04:21 PM, Ian Lance Taylor wrote: On Tue, Mar 14, 2017 at 3:20 AM, Denis Khalikov

Re: [PATCH][PR sanitizer/77631] Support separate debug info in libbacktrace

On Tue, Mar 14, 2017 at 3:20 AM, Denis Khalikov wrote: > Thanks for review, > >> Skimming over the patch I noticed you duplicate libiberties xcrc32 >> functionality. > > should i take care about standalone libbacktrace ? >

Re: [PATCH] Fix PR79908

> On Mar 14, 2017, at 3:57 AM, Richard Biener > wrote: > > On Tue, Mar 14, 2017 at 1:04 AM, Bill Schmidt > wrote: >> >> Index: gcc/tree-stdarg.c >> === >> ---

Re: [PATCH] gcov: Mark BBs that do not correspond to a line in source code (PR gcov-profile/79891).

On 03/14/2017 01:33 PM, Richard Biener wrote: > On Tue, 14 Mar 2017, Martin Liška wrote: > >> On 03/14/2017 11:48 AM, Richard Biener wrote: >>> On Tue, 14 Mar 2017, Martin Liška wrote: >>> On 03/14/2017 11:30 AM, Richard Biener wrote: > On Tue, 14 Mar 2017, Martin Liška wrote: >

Re: [PATCH] gcov: Mark BBs that do not correspond to a line in source code (PR gcov-profile/79891).

On Tue, 14 Mar 2017, Richard Biener wrote: > On Tue, 14 Mar 2017, Martin Liška wrote: > > > > /tmp/gcov-1.gcno: block > > 2:`/home/marxin/Programming/gcc/gcc/testsuite/gcc.misc-tests/gcov-1.c':10, > > 14 > > /tmp/gcov-1.gcno: block > >

Re: [PATCH] gcov: Mark BBs that do not correspond to a line in source code (PR gcov-profile/79891).

On Tue, 14 Mar 2017, Martin Liška wrote: > On 03/14/2017 11:48 AM, Richard Biener wrote: > > On Tue, 14 Mar 2017, Martin Liška wrote: > > > >> On 03/14/2017 11:30 AM, Richard Biener wrote: > >>> On Tue, 14 Mar 2017, Martin Liška wrote: > >>> > On 03/14/2017 11:13 AM, Richard Biener wrote: >

[PATCH] Install gcov-dump.

Tested on my local machine that's properly installed. Ready for trunk? Thanks, Martin >From 553c8402f8b0c77a30f4476918de1e4acff34dbc Mon Sep 17 00:00:00 2001 From: marxin Date: Tue, 14 Mar 2017 13:26:49 +0100 Subject: [PATCH] Install gcov-dump. gcc/ChangeLog: 2017-03-14 Martin

GCC 7.1 Status report (2017-03-14)

Status == The trunk is in regression and documentation fixes mode (Stage 4) thus as if it were a release branch. We are feature complete since quite a while and just chasing down P1 bugs which block the release of GCC 7. Tentative release date is mid April which means, given past history,

[PATCH] [PR79542][Ada] Fix ICE in dwarf2out.c with nested func. inlining

Hello, https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79542 reports an ICE in dwarf2out.c for an Ada testcase built with optimization. This crash happens during the late generation pass because add_gnat_descriptive_type cannot find the type DIE corresponding to some descriptive type after having

Re: [PATCH 4/N] Do not ICE on an invalid input for MV.

On 03/14/2017 12:09 PM, Richard Biener wrote: > On Tue, Mar 14, 2017 at 11:24 AM, Martin Liška wrote: >> Hello. >> >> This fixes ICE when one does not provide valid target names: >> __attribute__((target_clones("default,foo,bar"))) >> >> In that situation I suggest to print: >> >>

Re: [PATCH] gcov: Mark BBs that do not correspond to a line in source code (PR gcov-profile/79891).

On 03/14/2017 12:55 PM, Martin Liška wrote: > On 03/14/2017 11:48 AM, Richard Biener wrote: >> On Tue, 14 Mar 2017, Martin Liška wrote: >> >>> On 03/14/2017 11:30 AM, Richard Biener wrote: On Tue, 14 Mar 2017, Martin Liška wrote: > On 03/14/2017 11:13 AM, Richard Biener wrote: >>

Re: [PATCH] gcov: Mark BBs that do not correspond to a line in source code (PR gcov-profile/79891).

On 03/14/2017 11:48 AM, Richard Biener wrote: > On Tue, 14 Mar 2017, Martin Liška wrote: > >> On 03/14/2017 11:30 AM, Richard Biener wrote: >>> On Tue, 14 Mar 2017, Martin Liška wrote: >>> On 03/14/2017 11:13 AM, Richard Biener wrote: > On Tue, 14 Mar 2017, Martin Liška wrote: >

Re: [PATCH 2] Fix multiple target clones nodes (PR lto/66295).

On Tue, Mar 14, 2017 at 12:04 PM, Martin Liška wrote: > On 03/14/2017 11:29 AM, Richard Biener wrote: >> On Tue, Mar 14, 2017 at 11:09 AM, Martin Liška wrote: >>> On 03/14/2017 10:46 AM, Richard Biener wrote: On Mon, Mar 13, 2017 at 4:19 PM, Martin Liška

Re: [PATCH 4/N] Do not ICE on an invalid input for MV.

On Tue, Mar 14, 2017 at 11:24 AM, Martin Liška wrote: > Hello. > > This fixes ICE when one does not provide valid target names: > __attribute__((target_clones("default,foo,bar"))) > > In that situation I suggest to print: > > $ ./xgcc -B. /tmp/mvc-ice.c > /tmp/mvc-ice.c:6:1:

Re: [PATCH 3/3] Verify that target can create a dispatcher call (PR target/79892).

On Mon, Mar 13, 2017 at 9:26 AM, marxin wrote: > gcc/ChangeLog: Ok. Richard. > 2017-03-13 Martin Liska > > * multiple_target.c (create_dispatcher_calls): Check that > a target can create a function dispatcher. > --- > gcc/multiple_target.c |

Re: [PATCH 2] Fix multiple target clones nodes (PR lto/66295).

On 03/14/2017 11:29 AM, Richard Biener wrote: > On Tue, Mar 14, 2017 at 11:09 AM, Martin Liška wrote: >> On 03/14/2017 10:46 AM, Richard Biener wrote: >>> On Mon, Mar 13, 2017 at 4:19 PM, Martin Liška wrote: Hello. This is a small follow-up patch,

Re: [PATCH] gcov: Mark BBs that do not correspond to a line in source code (PR gcov-profile/79891).

On Tue, 14 Mar 2017, Martin Liška wrote: > On 03/14/2017 11:30 AM, Richard Biener wrote: > > On Tue, 14 Mar 2017, Martin Liška wrote: > > > >> On 03/14/2017 11:13 AM, Richard Biener wrote: > >>> On Tue, 14 Mar 2017, Martin Liška wrote: > >>> > On 03/14/2017 10:12 AM, Richard Biener wrote: >

Re: [PATCH] gcov: Mark BBs that do not correspond to a line in source code (PR gcov-profile/79891).

On 03/14/2017 11:30 AM, Richard Biener wrote: > On Tue, 14 Mar 2017, Martin Liška wrote: > >> On 03/14/2017 11:13 AM, Richard Biener wrote: >>> On Tue, 14 Mar 2017, Martin Liška wrote: >>> On 03/14/2017 10:12 AM, Richard Biener wrote: > On Tue, 14 Mar 2017, Martin Liška wrote: >

Re: [PATCH] gcov: Mark BBs that do not correspond to a line in source code (PR gcov-profile/79891).

On Tue, 14 Mar 2017, Martin Liška wrote: > On 03/14/2017 11:13 AM, Richard Biener wrote: > > On Tue, 14 Mar 2017, Martin Liška wrote: > > > >> On 03/14/2017 10:12 AM, Richard Biener wrote: > >>> On Tue, 14 Mar 2017, Martin Liška wrote: > >>> > On 03/14/2017 09:13 AM, Richard Biener wrote: >

Re: [PATCH 2] Fix multiple target clones nodes (PR lto/66295).

On Tue, Mar 14, 2017 at 11:09 AM, Martin Liška wrote: > On 03/14/2017 10:46 AM, Richard Biener wrote: >> On Mon, Mar 13, 2017 at 4:19 PM, Martin Liška wrote: >>> Hello. >>> >>> This is a small follow-up patch, where local.local flag should be also >>> dropped >>>

[PATCH 4/N] Do not ICE on an invalid input for MV.

Hello. This fixes ICE when one does not provide valid target names: __attribute__((target_clones("default,foo,bar"))) In that situation I suggest to print: $ ./xgcc -B. /tmp/mvc-ice.c /tmp/mvc-ice.c:6:1: error: attribute(target("foo")) is unknown foo () ^~~ /tmp/mvc-ice.c:6:1: error:

Re: [PATCH][PR sanitizer/77631] Support separate debug info in libbacktrace

Thanks for review, > Skimming over the patch I noticed you duplicate libiberties xcrc32 > functionality. should i take care about standalone libbacktrace ? https://github.com/ianlancetaylor/libbacktrace > Also the additions to posix.c probably belong to dwarf.c and elf.c (the feature > is

Re: [PATCH] gcov: Mark BBs that do not correspond to a line in source code (PR gcov-profile/79891).

On 03/14/2017 11:13 AM, Richard Biener wrote: > On Tue, 14 Mar 2017, Martin Liška wrote: > >> On 03/14/2017 10:12 AM, Richard Biener wrote: >>> On Tue, 14 Mar 2017, Martin Liška wrote: >>> On 03/14/2017 09:13 AM, Richard Biener wrote: > On Tue, 14 Mar 2017, Martin Liška wrote: >

Re: [PATCH] gcov: Mark BBs that do not correspond to a line in source code (PR gcov-profile/79891).

On Tue, 14 Mar 2017, Martin Liška wrote: > On 03/14/2017 10:12 AM, Richard Biener wrote: > > On Tue, 14 Mar 2017, Martin Liška wrote: > > > >> On 03/14/2017 09:13 AM, Richard Biener wrote: > >>> On Tue, 14 Mar 2017, Martin Liška wrote: > >>> > On 03/13/2017 04:16 PM, Richard Biener wrote: >

Re: [PATCH 2] Fix multiple target clones nodes (PR lto/66295).

On 03/14/2017 10:46 AM, Richard Biener wrote: > On Mon, Mar 13, 2017 at 4:19 PM, Martin Liška wrote: >> Hello. >> >> This is a small follow-up patch, where local.local flag should be also >> dropped >> for a default implementation. >> >> Patch can bootstrap on x86_64-linux-gnu

Re: [PATCH 1/7] Add missing punctuation to message (PR driver/79875)

On 11 March 2017 11:28:46 CET, Roland Illig wrote: >Am 10.03.2017 um 05:12 schrieb Martin Sebor: >> I have just an observation/question here for future consideration. >> If this sort of diagnostic is common (I count 23 instances of it) >> or if it is expected to become

Re: [PATCH] gcov: Mark BBs that do not correspond to a line in source code (PR gcov-profile/79891).

On 03/14/2017 10:12 AM, Richard Biener wrote: > On Tue, 14 Mar 2017, Martin Liška wrote: > >> On 03/14/2017 09:13 AM, Richard Biener wrote: >>> On Tue, 14 Mar 2017, Martin Liška wrote: >>> On 03/13/2017 04:16 PM, Richard Biener wrote: > On Mon, 13 Mar 2017, Martin Liška wrote: >

Re: [PATCH 2] Fix multiple target clones nodes (PR lto/66295).

On Mon, Mar 13, 2017 at 4:19 PM, Martin Liška wrote: > Hello. > > This is a small follow-up patch, where local.local flag should be also dropped > for a default implementation. > > Patch can bootstrap on x86_64-linux-gnu and survives regression tests. > > Ready to be installed? I

Re: [RFC][PATCH][AArch64] Improve generic branch cost

On Thu, Mar 09, 2017 at 02:06:16PM -0800, Andrew Pinski wrote: > On Thu, Mar 9, 2017 at 6:42 AM, Wilco Dijkstra wrote: > > Hi, > > > > Recently we've put a lot of effort into improving ifcvt to use CSEL on > > AArch64. In

Re: [PATCH] [ADA] Fix bootstrap failure on mips64el-linux-gnuabi64

On 13.03.2017 18:26, James Cowgill wrote: > Hi, > > On 11/03/17 12:11, Arnaud Charlet wrote: >>> This patch fixes an error caused by my changing of the signal constants >>> on MIPS in r244026. While that patch worked on mipsel, ada fails to >>> bootstrap with it on mips64el with the error: >>>

  1   2   >