Go patch committed: Use VIEW_CONVERT_EXPR where needed

This patch to the Go frontend's GCC interface uses VIEW_CONVERT_EXPR where needed. The code was using fold_convert_loc in constructor_expression and temporary_variable, which almost always worked. However, it failed in https://golang.org/issue/23606. This patch fixes the problem. Bootstrapped

[PATCH][RFA][PR target/84128] Fix restore of scratch register used in probing loops

Whee, fun, this appears to have been broken for a very long time, possibly since the introduction of -fstack-check in 2010. Thankfully it only affects 32 bit and only in relatively constrained circumstances. -fstack-check and -fstack-clash both potentially create a loop for stack probing. In

Re: [PATCH][PR target/84064] Fix assertion with -fstack-clash-protection

On 01/30/2018 12:23 AM, Uros Bizjak wrote: > On Tue, Jan 30, 2018 at 5:48 AM, Jeff Law wrote: >> >> >> >> stack-clash-protection will sometimes force a prologue to use pushes to >> save registers. We try to limit how often that happens as it constrains >> options for generating

[PATCH] libgcc: xtensa: fix build with -mtext-section-literals

libgcc/ 2018-01-31 Max Filippov * config/xtensa/ieee754-df.S (__adddf3_aux): Add .literal_position directive. * config/xtensa/ieee754-sf.S (__addsf3_aux): Likewise. --- libgcc/config/xtensa/ieee754-df.S | 1 + libgcc/config/xtensa/ieee754-sf.S | 1 +

Go patch committed: Function_type and Backend_function_type are not identical

This patch by Cherry Zhang fixes the Go frontend so that Function_type and Backend_function_type are not identical, since they have different backend representations. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline. Ian Index: gcc/go/gofrontend/MERGE

Re: [PATCH] Fix -traditional-cpp preprocessing ICE (PR preprocessor/69869)

On Tue, 30 Jan 2018, Jakub Jelinek wrote: > Hi! > > This restores GCC 3.3 behavior on this testcase, before 3.4 started ICEing > on it when it started to use the common block comment skipping code for > -traditional-cpp and just a simple function for macro block comments has > been added. Even

Re: [PATCH] Mark falign-*= as Optimization (PR c/84100)

On Tue, 30 Jan 2018, Jakub Jelinek wrote: > Hi! > > While -falign-{functions,jumps,labels,loops} are marked Optimization, > -falign-{functions,jumps,labels,loops}= are not. They use the same Var(), > for that it makes no difference, but it means we reject them in optimize > attribute starting

New Finnish PO file for 'cpplib' (version 8.1-b20180128)

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

Contents of PO file 'cpplib-8.1-b20180128.fi.po'

cpplib-8.1-b20180128.fi.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator.

Re: Fix LRA subreg calculation for big-endian targets

> OK. Makes me wonder how many big endian LRA targets are getting significant > use. Debian still has an active SPARC64 port now based on GCC 7 with LRA. -- Eric Botcazou

Re: [wwwdocs] GCC-7.3 changes: Add note about LEON3FT erratum workaround

> I would like to commit the following comment about LEON3-FT errata now > available in GCC-7.3. Fine with me, thanks. -- Eric Botcazou

Re: [PR tree-optimization/84047] missing -Warray-bounds on an out-of-bounds index

On 01/30/2018 03:11 PM, Aldy Hernandez wrote: Hi! [Note: Jakub has mentioned that missing -Warray-bounds regressions should be punted to GCC 9. I think this particular one is easy pickings, but if this and/or the rest of the -Warray-bounds regressions should be marked as GCC 9 material, please

[PATCH] correct -Wrestrict handling of arrays of arrays (PR 84095)

Testing GCC 8 with recent Linux kernel sources has uncovered a bug in the handling of arrays of arrays by the -Wrestrict checker where it fails to take references to different array elements into consideration, issuing false positives. The attached patch corrects this mistake. In addition, to

Re: [PATCH] Fix debug info after the fortran descriptor changes (PR debug/84131)

On Tue, Jan 30, 2018 at 11:53:40PM +0100, Jakub Jelinek wrote: > > DW_AT_data_location needs to be the data pointer, which is at offset 0, > but we were emitting a bogus +8 in that case (+4 for 32-bit targets). > > With this patch, the change on -g -dA is: > - .uleb128 0x4#

[PATCH] Fix debug info after the fortran descriptor changes (PR debug/84131)

Hi! DW_AT_data_location needs to be the data pointer, which is at offset 0, but we were emitting a bogus +8 in that case (+4 for 32-bit targets). With this patch, the change on -g -dA is: - .uleb128 0x4# DW_AT_data_location + .uleb128 0x2# DW_AT_data_location .byte

[PATCH] Fix -traditional-cpp preprocessing ICE (PR preprocessor/69869)

Hi! This restores GCC 3.3 behavior on this testcase, before 3.4 started ICEing on it when it started to use the common block comment skipping code for -traditional-cpp and just a simple function for macro block comments has been added. Even the macro block comments can be not properly terminated

[PATCH] Mark falign-*= as Optimization (PR c/84100)

Hi! While -falign-{functions,jumps,labels,loops} are marked Optimization, -falign-{functions,jumps,labels,loops}= are not. They use the same Var(), for that it makes no difference, but it means we reject them in optimize attribute starting with r237174. Fixed thusly, bootstrapped/regtested on

[PATCH, rs6000] Fix VSX/altivec assumptions in altivec-13.c testcase

Hi, Some VSX function has previosly crept into the altivec-13 testcase. In particular, anything 'vector long long' and 'vector double', causing issues on platforms without VSX support. So, break that content out into it's own testcase, allowing better testcase coverage. Sniff-tested on

Re: Fix ipa-inline ICE

On Tue, Jan 30, 2018 at 09:05:31PM +0100, Rainer Orth wrote: > > this patch fixed ICE that was introduced by Richard Standiford's change to > > reorder > > can and want_inline predicates to reduce amount of work done to verify > > inlining limits. > > This bypasses check that the function is

[patch, fortran, committed] Fix PR 84134

Hello world, another obvious fix, this time for an ice-on-invalid regression, committed after regression-testing. Regards Thomas 2017-01-30 Thomas Koenig PR fortran/84134 * array.c (gfc_ref_dimen_size): Whitespace fixes. If stride is

Re: [PATCH] PR 78534 Reinstate better string copy algorithm

OK. Thought I already sent OK, but must of got side track with work. -- steve On Tue, Jan 30, 2018 at 06:25:31PM +0200, Janne Blomqvist wrote: > PING > > On Tue, Jan 23, 2018 at 3:31 PM, Janne Blomqvist > wrote: > > As part of the change to larger character

[PR tree-optimization/84047] missing -Warray-bounds on an out-of-bounds index

Hi! [Note: Jakub has mentioned that missing -Warray-bounds regressions should be punted to GCC 9. I think this particular one is easy pickings, but if this and/or the rest of the -Warray-bounds regressions should be marked as GCC 9 material, please let me know so we can adjust all relevant

Re: [C++ PATCH] Speed up inplace_merge algorithm & fix inefficient logic(PR c++/83938)

Your change looks good, don't hesitate to re-submit a proper patch with the point 1 below fix. You should add gcc-patches@gcc.gnu.org when you do so. Remaining questions will be: Copyright assignment, your change seems limited enough to avoid it but you will need an official maintainer

[Patch, Fortran, committed] fix bracket in dejagnu directive

Hi all, I have just committed an obvious patch that adds a closing bracket in a dg-options directive in the testsuite as r257208: Index: gcc/testsuite/gfortran.dg/pr68318_1.f90 === --- gcc/testsuite/gfortran.dg/pr68318_1.f90

Re: Link with correct values-*.o files on Solaris (PR target/40411)

Hi Jonathan, > On 30/01/18 15:51 +0100, Rainer Orth wrote: >>Hi Joseph, >> >>> On Tue, 30 Jan 2018, Rainer Orth wrote: >>> So it seems the following snippet #define STARTFILE_ARCH_SPEC \ [...] %{std=c9*|std=iso9899\\:199409|std=c1*:values-Xc.o%s; :values-Xa.o%s}

Re: [SFN+LVU+IEPM v4 7/9] [LVU] Introduce location views

Alexandre Oliva writes: > On Jan 26, 2018, Jakub Jelinek wrote: > >> Having to tweak debug info consumers so that they treat DW_LLE_* of 9 >> one way for .debug_loclist of version 5 and another way for .debug_loclist >> of version 6 isn't a good idea. > >

[patch, fortran, committed] Fix PR 84133, regression with matmul

Hello world, I have just committed the attached patch as obvious, after regtesting. Regards Thomas 2018-01-30 Thomas Koenig PR fortran/84133 * frontend-passes (matmul_to_var_expr): Return early if in association list.

Re: patch to fix PR84112

On 01/30/2018 03:37 PM, Rainer Orth wrote: Hi Vladimir, The following patch fixes https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84112 The patch was successfully bootstrapped and tested on x86-64 and ppc64. Committed as rev. 257204. [...] Index: testsuite/ChangeLog

Re: patch to fix PR84112

Hi Vladimir, > The following patch fixes > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84112 > > The patch was successfully bootstrapped and tested on x86-64 and ppc64. > > Committed as rev. 257204. [...] > Index: testsuite/ChangeLog >

patch to fix PR84112

The following patch fixes https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84112 The patch was successfully bootstrapped and tested on x86-64 and ppc64. Committed as rev. 257204. Index: ChangeLog === --- ChangeLog (revision

Fix gnat.dg/lto20.adb XPASS

This patch 2018-01-30 Jan Hubicka gcc: PR lto/83954 * lto-symtab.c (warn_type_compatibility_p): Silence false positive for type match warning on arrays of pointers. gcc/testsuite: PR lto/83954 * gcc.dg/lto/pr83954.h: New

C++ PATCH to fix ICE in generic lambda with user-defined conversion (PR c++/84125)

This testcase breaks since r256550 because we end up trying to build_address of a CONSTRUCTOR, but that doesn't work because we hit gcc_checking_assert (TREE_CODE (t) != CONSTRUCTOR); finish_static_assert gets {} as 'condition'. In the testcase we have a user-defined conversion, so {} should

Re: Fix ipa-inline ICE

On January 30, 2018 9:05:31 PM GMT+01:00, Rainer Orth wrote: >Hi Jan, > >> this patch fixed ICE that was introduced by Richard Standiford's >change to reorder >> can and want_inline predicates to reduce amount of work done to >verify inlining limits. >> This

Re: Fix ipa-inline ICE

Hi Jan, > this patch fixed ICE that was introduced by Richard Standiford's change to > reorder > can and want_inline predicates to reduce amount of work done to verify > inlining limits. > This bypasses check that the function is optimized that makes inliner to ICE > because > function summary

C++ PATCH for c++/84091, ICE with local class in lambda in template

Another refinement to local class handling in determine_visibility. If we're looking at a local class inside a lambda, it thinks it is in a template but the lambda isn't a template instantiation. So look for the enclosing template context to use. Tested x86_64-pc-linux-gnu, applying to trunk.

C++ PATCH for c++/84098, ICE with lambda in template NSDMI

When instantiating the members of a class template, we don't need to consider lambdas, as instantiating them will be handled when we get to tsubst_lambda_expr. And now the new assert catches places we were failing to ignore them, as here. Tested x86_64-pc-linux-gnu, applied to trunk. commit

Re: [PATCH] Use pointer sized array indices.

Hi Janne, PING**2 OK. Regards, Thomas

Re: [PING^3] [PATCH] Remove CANADIAN, that break compilation for foreign target

On Tue, 30 Jan 2018 12:54:21 + Jonathan Wakely wrote: > On 30/01/18 10:19 +0300, Petr Ovtchenkov wrote: > >On Tue, 19 Dec 2017 11:37:43 +0300 > >Petr Ovtchenkov wrote: > > > >ping^3 > > > I don't fully understand the consequences (or need) for this

[PR lto/84105] handle TYPE_IDENTIFIERs for FUNCTION_TYPEs in the gimple pretty printer

Hi! As discussed in the PR, the ICE here happens in dump_generic_node: case FUNCTION_TYPE: case METHOD_TYPE: ... if (TYPE_NAME (node) && DECL_NAME (TYPE_NAME (node))) dump_decl_name (pp, TYPE_NAME (node), flags); (gdb) print node $21 = (gdb) print node.type_common.name

Re: [PATCH] Fix sched-deps.c handling of frame related insns (PR rtl-optimization/83986)

On 01/30/2018 11:11 AM, Jakub Jelinek wrote: Hi! We don't want to move /f instructions across jumps in either direction, sched_analyze_insn has code for that by adding the insn into sched_before_next_jump list and by adding anti dependence against pending_jump_insns. That works fine, as long

Re: [SFN+LVU+IEPM v4 7/9] [LVU] Introduce location views

On Jan 26, 2018, Jakub Jelinek wrote: > Having to tweak debug info consumers so that they treat DW_LLE_* of 9 > one way for .debug_loclist of version 5 and another way for .debug_loclist > of version 6 isn't a good idea. Maybe we don't have to do that. The reason I

Re: [PR81611] improve auto-inc

On Jan 25, 2018, Alexandre Oliva wrote: > Thanks, I'll retest with the simplified test (just in case; for I can't > recall why I ended up with all those redundant conditions), As suspected, removing the redundant tests didn't regress anything. I suppose they mattered in some

Re: [PATCH] make -Wrestrict for strcat more meaningful (PR 83698)

Ping: https://gcc.gnu.org/ml/gcc-patches/2018-01/msg01488.html This is a minor improvement but there have been a couple of comments lately pointing out that the numbers in the -Wrestrict messages can make them confusing. Jakub, since you made one of those comments (the other came up in the

Re: [PATCH, rs6000][PR debug/83758] v2 rs6000_internal_arg_pointer should only return a register

Hi! On Tue, Jan 30, 2018 at 10:21:33AM -0600, Aaron Sawdey wrote: > This fix looks good, passes bootstrap, go tests run. > > Segher is currently regtesting on ppc64le power9. OK for trunk if tests > pass? > > 2018-01-30 Aaron Sawdey > > *

Re: [patch, libfortran] Adapt handling of derived types to new dtype

On Mon, Jan 29, 2018 at 11:51 PM, Thomas Koenig wrote: > Hello world, > > this patch fixes the library issues left over from Paul's rank-15 patch > by removing the GFC_DTYPE_DERIVED_* macros and (mostly) handling these > cases separately. > > The problem was with folding

Re: [PATCH] Use pointer sized array indices.

PING**2 On Wed, Jan 17, 2018 at 8:02 PM, Janne Blomqvist wrote: > PING > > On Fri, Dec 29, 2017 at 8:28 PM, Janne Blomqvist > wrote: >> On Fri, Dec 29, 2017 at 7:17 PM, Thomas Koenig wrote: >>> Hi Janne, >>>

Re: [PATCH] PR 78534 Reinstate better string copy algorithm

PING On Tue, Jan 23, 2018 at 3:31 PM, Janne Blomqvist wrote: > As part of the change to larger character lengths, the string copy > algorithm was temporarily pessimized to get around some spurious > -Wstringop-overflow warnings. Having tried a number of variations of

Re: [PATCH, rs6000][PR debug/83758] v2 rs6000_internal_arg_pointer should only return a register

On Tue, Jan 30, 2018 at 10:21:33AM -0600, Aaron Sawdey wrote: > 2018-01-30 Aaron Sawdey > > * config/rs6000/rs6000.c (rs6000_internal_arg_pointer ): Only return No space before ): . Will defer ack to Segher or David. > a reg rtx. > Index:

Re: [PATCH, rs6000][PR debug/83758] v2 rs6000_internal_arg_pointer should only return a register

On Tue, 2018-01-30 at 14:04 +0100, Jakub Jelinek wrote: > On IRC when discussing it with Segher this morning we've come to the > conclusion that it would be best if rs6000 just followed what all > other > ports to, i.e. return a pseudo from the target hook, like: > > ---

[PATCH] Fix sched-deps.c handling of frame related insns (PR rtl-optimization/83986)

Hi! We don't want to move /f instructions across jumps in either direction, sched_analyze_insn has code for that by adding the insn into sched_before_next_jump list and by adding anti dependence against pending_jump_insns. That works fine, as long as we don't flush the dependency lists,

Re: [PR83370][AARCH64]Use tighter register constraints for sibcall patterns.

Hi Richard, Thanks for the review! On 29/01/18 20:23, Richard Sandiford wrote: The patch looks good to me FWIW. How about adding something like the following testcase? /* { dg-do run } */ /* { dg-options "-O2" } */ typedef void (*fun) (void); void

Re: Link with correct values-*.o files on Solaris (PR target/40411)

On 30/01/18 15:51 +0100, Rainer Orth wrote: Hi Joseph, On Tue, 30 Jan 2018, Rainer Orth wrote: So it seems the following snippet #define STARTFILE_ARCH_SPEC \ [...] %{std=c9*|std=iso9899\\:199409|std=c1*:values-Xc.o%s; :values-Xa.o%s} \ seems like the right thing to do, as you said.

Re: Link with correct values-*.o files on Solaris (PR target/40411)

Hi Joseph, > On Tue, 30 Jan 2018, Rainer Orth wrote: > >> So it seems the following snippet >> >> #define STARTFILE_ARCH_SPEC \ >> [...] >> %{std=c9*|std=iso9899\\:199409|std=c1*:values-Xc.o%s; :values-Xa.o%s} \ >> >> seems like the right thing to do, as you said. > > That version would

Re: [PATCH][PR target/84066] Wrong shadow stack register size is saved for x32

On Tue, Jan 30, 2018 at 6:38 AM, Uros Bizjak wrote: > On Tue, Jan 30, 2018 at 3:19 PM, Tsimbalist, Igor V > wrote: >> x32 is a 64-bit process with 32-bit software pointer and kernel may >> place x32 shadow stack above 4GB. We need to save and

Re: Link with correct values-*.o files on Solaris (PR target/40411)

On Tue, 30 Jan 2018, Rainer Orth wrote: > So it seems the following snippet > > #define STARTFILE_ARCH_SPEC \ > [...] > %{std=c9*|std=iso9899\\:199409|std=c1*:values-Xc.o%s; :values-Xa.o%s} \ > > seems like the right thing to do, as you said. That version would need updating when we add

Re: [PATCH][PR target/84066] Wrong shadow stack register size is saved for x32

On Tue, Jan 30, 2018 at 3:19 PM, Tsimbalist, Igor V wrote: > x32 is a 64-bit process with 32-bit software pointer and kernel may > place x32 shadow stack above 4GB. We need to save and restore 64-bit > shadow stack register for x32. builtin jmp buf size is 5

Re: [PATCH] Fix PR84101, account for function ABI details in vectorization costs

On Tue, 30 Jan 2018, Richard Biener wrote: > > This patch tries to deal with the "easy" part of a function ABI, > the return value location, in vectorization costing. The testcase > shows that if we vectorize the returned value but the function > doesn't return in memory or in a vector register

[PATCH][PR target/84066] Wrong shadow stack register size is saved for x32

x32 is a 64-bit process with 32-bit software pointer and kernel may place x32 shadow stack above 4GB. We need to save and restore 64-bit shadow stack register for x32. builtin jmp buf size is 5 pointers. We have space to save 64-bit shadow stack pointer: 32-bit SP, 32-bit FP, 32-bit IP, 64-bit

Re: Link with correct values-*.o files on Solaris (PR target/40411)

Hi Joseph, > On Fri, 12 Jan 2018, Rainer Orth wrote: > >> At the same time, I had a new look at when values-Xc.o is used by the >> Studio compilers. It selects strict ISO C mode in a couple of cases, >> and the latest Studio 12.6 cc, which is about to do away with the >> previous -Xc option

Fix template for ipa-inline-2.c and ipa-inline-3.c

Hi, this PR is about rounding issue of sreal->integer conversion. I converted the whole code to sreals but the change seems bit too big and with no practical improvement to be justifiable, so this patch goes by simply fixing the template for current roundoff error. Hopefully counter code is now

Fix ipa-inline ICE

Hi, this patch fixed ICE that was introduced by Richard Standiford's change to reorder can and want_inline predicates to reduce amount of work done to verify inlining limits. This bypasses check that the function is optimized that makes inliner to ICE because function summary is missing. This

Re: [PATCH][PR debug/83758] look more carefully for internal_arg_pointer in vt_add_function_parameter()

On Tue, Jan 30, 2018 at 06:50:50AM -0600, Aaron Sawdey wrote: > > Anyway, my preference would be to change that gen_rtx_PLUS into > > stack_parm = crtl->args.internal_arg_pointer; > > if (!CONST_INT_P (offset_rtx)) > > stack_parm = gen_rtx_PLUS (Pmode, stack_parm, offset_rtx); > > else

Re: [PING^3] [PATCH] Remove CANADIAN, that break compilation for foreign target

On 30/01/18 10:19 +0300, Petr Ovtchenkov wrote: On Tue, 19 Dec 2017 11:37:43 +0300 Petr Ovtchenkov wrote: ping^3 I don't fully understand the consequences (or need) for this patch. I asked some other people to look at it, and didn't get confirmation it's OK. So I'm

Re: [PATCH][PR debug/83758] look more carefully for internal_arg_pointer in vt_add_function_parameter()

On Tue, 2018-01-30 at 11:13 +0100, Jakub Jelinek wrote: > On Tue, Jan 30, 2018 at 03:55:58AM -0600, Segher Boessenkool wrote: > > > But in that case, what does the copying? > > > > I don't know. Aaron will look at it, but timezones etc. :-) Indeed I did see unshare_all_rtl() copying

Contents of PO file 'cpplib-8.1-b20180128.pt_BR.po'

cpplib-8.1-b20180128.pt_BR.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator.

New Brazilian Portuguese PO file for 'cpplib' (version 8.1-b20180128)

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

RE: [patch][x86] -march=icelake

Thank you for your comments, fixed them and rebased Ice Lake patch on top of it. Ok for trunk? Bitmask patch changelog: gcc/c-family/ * c-common.h (omp_clause_mask): Move to wide_int_bitmask.h. gcc/ * config/i386/i386.c (ix86_option_override_internal): Change flags type to

Re: [PATCH] Fix PR83008

On Tue, Jan 30, 2018 at 11:07:50AM +0100, Richard Biener wrote: > > I have been asked to push this change, fixing (somewhat) the impreciseness > of costing constant/invariant vector uses in SLP stmts. The previous > code always just considered a single constant to be generated in the > prologue

Re: [PATCH][PR debug/83758] look more carefully for internal_arg_pointer in vt_add_function_parameter()

On Tue, Jan 30, 2018 at 03:55:58AM -0600, Segher Boessenkool wrote: > > But in that case, what does the copying? > > I don't know. Aaron will look at it, but timezones etc. :-) > > > That's what seems strange. I can see why we'd have two nested > > pluses with the inner plus being

[PATCH] Fix PR83008

I have been asked to push this change, fixing (somewhat) the impreciseness of costing constant/invariant vector uses in SLP stmts. The previous code always just considered a single constant to be generated in the prologue irrespective of how many we'd need. With this patch we properly handle

Re: [PATCH][PR debug/83758] look more carefully for internal_arg_pointer in vt_add_function_parameter()

Segher Boessenkool writes: > On Tue, Jan 30, 2018 at 09:41:47AM +, Richard Sandiford wrote: >> Segher Boessenkool writes: >> > On Mon, Jan 29, 2018 at 11:41:32PM +0100, Jakub Jelinek wrote: >> >> On Mon, Jan 29, 2018 at 04:26:50PM

[PATCH] Fix PR84101, account for function ABI details in vectorization costs

This patch tries to deal with the "easy" part of a function ABI, the return value location, in vectorization costing. The testcase shows that if we vectorize the returned value but the function doesn't return in memory or in a vector register but as in this case in an integer register pair

Re: [PATCH][PR debug/83758] look more carefully for internal_arg_pointer in vt_add_function_parameter()

On Tue, Jan 30, 2018 at 09:41:47AM +, Richard Sandiford wrote: > Segher Boessenkool writes: > > On Mon, Jan 29, 2018 at 11:41:32PM +0100, Jakub Jelinek wrote: > >> On Mon, Jan 29, 2018 at 04:26:50PM -0600, Segher Boessenkool wrote: > >> > > The code actually meant

Re: [PATCH] [PR testsuite/81010] Fix PPC test

On Jan 29 2018, Jeff Law wrote: > On 01/07/2018 10:09 AM, Segher Boessenkool wrote: >> Hi! >> >> On Sun, Jan 07, 2018 at 12:58:25AM -0700, Jeff Law wrote: >>> diff --git a/gcc/testsuite/gcc.target/powerpc/pr56605.c >>> b/gcc/testsuite/gcc.target/powerpc/pr56605.c >>> index

Re: [PATCH][PR debug/83758] look more carefully for internal_arg_pointer in vt_add_function_parameter()

Segher Boessenkool writes: > On Mon, Jan 29, 2018 at 11:41:32PM +0100, Jakub Jelinek wrote: >> On Mon, Jan 29, 2018 at 04:26:50PM -0600, Segher Boessenkool wrote: >> > > The code actually meant pointer comparison, the question is what is >> > > different on powerpc*

Re: [PATCH] Fix SCEV ICE during cunroll (PR tree-optimization/84111)

On Tue, 30 Jan 2018, Jakub Jelinek wrote: > On Tue, Jan 30, 2018 at 08:59:43AM +0100, Richard Biener wrote: > > The issue is that > > > > static bool > > tree_unroll_loops_completely_1 (bool may_increase_size, bool unroll_outer, > > bitmap father_bbs, struct loop

Re: [patch][x86] -march=icelake

On Tue, Jan 30, 2018 at 08:35:38AM +, Koval, Julia wrote: > * c-common.h (omp_clause_mask): Move to wide_int_bitmask.h Missing dot ad the end. + wide_int_bitmask PTA_3DNOW (HOST_WIDE_INT_1U << 0); Can't all these be const wide_int_bitmask instead of just wide_int_bitmask? ... + +

Contents of PO file 'cpplib-8.1-b20180128.sv.po'

cpplib-8.1-b20180128.sv.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator.

New Swedish PO file for 'cpplib' (version 8.1-b20180128)

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

RE: [patch][x86] -march=icelake

Renamed it. Ok for trunk? gcc/c-family/ * c-common.h (omp_clause_mask): Move to wide_int_bitmask.h gcc/ * config/i386/i386.c (ix86_option_override_internal): Change flags type to wide_int_bitmask. * wide-int-bitmask.h: New. Thanks, Julia > -Original

Re: [PATCH] Fix SCEV ICE during cunroll (PR tree-optimization/84111)

On Tue, Jan 30, 2018 at 08:59:43AM +0100, Richard Biener wrote: > The issue is that > > static bool > tree_unroll_loops_completely_1 (bool may_increase_size, bool unroll_outer, > bitmap father_bbs, struct loop *loop) > { > struct loop *loop_father; > bool

New Russian PO file for 'gcc' (version 8.1-b20180128)

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 Russian team of translators. The file is available at: http://translationproject.org/latest/gcc/ru.po (This file, 'gcc-8.1-b20180128.ru.po',

[PATCH, i386, AVX] PR target/83828: fix AVX-512BITALG test failures

Hello, If masked variant of vpopcnt[w,q] is being issued: there's no way for reload to put 32/64 bit mask into mask register, since kmov[d,q] are only available under -mavx512bw switch. We can insist user to issue -mavx512bw along w/ -mavx512bitalg if she is going to use masked variants of

New Vietnamese PO file for 'cpplib' (version 8.1-b20180128)

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

Contents of PO file 'cpplib-8.1-b20180128.vi.po'

cpplib-8.1-b20180128.vi.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator.

Re: [PATCH] Fix SCEV ICE during cunroll (PR tree-optimization/84111)

On Mon, Jan 29, 2018 at 11:58:45PM -0700, Jeff Law wrote: > On 01/29/2018 04:37 PM, Jakub Jelinek wrote: > > Hi! > > > > As mentioned in the PR, cunroll sometimes registers some SSA_NAMEs for > > renaming and then invokes some SCEV using functions before finally updating > > the SSA form. On the

Re: [PATCH] Fix SCEV ICE during cunroll (PR tree-optimization/84111)

On Mon, 29 Jan 2018, Jeff Law wrote: > On 01/29/2018 04:37 PM, Jakub Jelinek wrote: > > Hi! > > > > As mentioned in the PR, cunroll sometimes registers some SSA_NAMEs for > > renaming and then invokes some SCEV using functions before finally updating > > the SSA form. On the testcase we end up