Re: [patch,openacc] C, C++ OpenACC wait diagnostic change

Hi Julian! On Mon, 3 Dec 2018 21:10:50 +, Julian Brown wrote: > On Fri, 30 Nov 2018 16:25:42 +0100 > Thomas Schwinge wrote: > > [...] > > I've made those changes in the attached, thank you. OK? Yes, thanks! Grüße Thomas > 2018-XX-YY James Norris > Cesar Philippidis >

[PATCH] Fix miscompiles with latest VRP change

Jeff noticed that some dfp stuff was miscompiled. I appearantly didn't notice the new assert registering isn't guarded by EQ/NE_EXPR thus the following makes it fancy. Bootstrapped and tested on x86_64-unknown-linux-gnu, applied. Richard. 2018-12-04 Richard Biener PR

Re: [committed] C++ PATCH to add test for c++/83856

On Mon, 3 Dec 2018 at 17:05, Marek Polacek wrote: > > On Mon, Dec 03, 2018 at 10:14:11AM +0100, Christophe Lyon wrote: > > This new test fails on arm and other targets according to > > gcc-testresults. On arm, I can see: > > /gcc/testsuite/g++.dg/cpp1y/lambda-generic-83856.C:6:27: fatal error: >

Re: [PATCH] Fix PR64242

On Tue, Dec 04, 2018 at 11:20:38AM +0100, Christophe Lyon wrote: > This commit didn't fix the failure I reported on some arm targets, and > it introduced > a regression on aarch64-none-elf with -mabi=ilp32: > FAIL: gcc.c-torture/execute/pr64242.c -O0 execution test > Il seems the test

Re: [PATCH] Fix PR64242

On Mon, 3 Dec 2018 at 17:26, Jakub Jelinek wrote: > > Hi! > > Here is a fix for the testcase, so that it doesn't FAIL pretty much > everywhere. > > On Fri, Nov 30, 2018 at 04:07:31PM -0700, Jeff Law wrote: > > > PR middle-end/64242 > > > * gcc.c-torture/execute/pr64242.c: New test. > >

[PATCH, libgo]: Use build.Default.Compiler in go/cmd/vet/types.goq

Without this patch go tool vet segfaults on alpha due to unknown architecture for gc compiler: go tool vet: exit status 2 panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=1 addr=24 pc=4832064492] goroutine 1 [running]: panic

[PATCH] Further rs6000 asm modifier tweaks (PR target/88188)

Hi! This patch adds further tweaks discussed in the last PR88188 mail. ccr_bit now returns -1 instead of failing assertions, so that the caller can decide what to do with it (fail assertion or output_operand_lossage with some reasonable diagnostics. For D and t it now requires CR_REGNO_P, so that

[PATCH] Fix P0634R3 - Down with typename! testsuite fallout

Hi! I've noticed these two tests now FAIL with -std=c++2a, they don't print any diagnostics. As I believe that was the point of the P0634R3 changes, this patch adjusts the testcases. Tested on x86_64-linux, ok for trunk? 2018-12-04 Jakub Jelinek *

Re: [PATCH AutoFDO/2]Treat ZERO as common profile probability/count

On Thu, Nov 29, 2018 at 12:20 AM Jan Hubicka wrote: > > > On Tue, Nov 20, 2018 at 6:55 PM bin.cheng > > wrote: > > > > > > Sender:Jan Hubicka > > > Sent at:2018 Nov 5 (Mon) 22:21 > > > To:Richard Biener > > > Cc:bin.cheng ; GCC Patches > > > > > > Subject:Re: [PATCH AutoFDO/2]Treat ZERO as

Fix ICE in pp_cxx_unqualified_id (PR c++/88348)

cxx_pretty_printer::type_id do not treat pointer to pointer to member correctly. this patch handle pointer to pointer to member according to C++ standard 11.3.3. I don't have write access to gcc. Bootstrapped/regtested on x86_64-linux Signed-off-by: Zhouyi Zhou 2018-12-04 Zhouyi Zhou

<    1   2