Substitute all "the the" with "the"

… by applying sed -i "s/the the/the/" `git grep -l "the the"`

[PATCH] PR88777, Out-of-range offsets building glibc test-tgmath2.c

bb-reorder is quite seriously broken if get_attr_min_length should return INT_MAX, which it does for hppa on branches with r267666. I went the wrong way with my min_attr_value r267666 change. It seems that it isn't important that a "can't calculate" value is returned from recursive calls, but

RE: [PATCH 6/9][GCC][AArch64] Add Armv8.3-a complex intrinsics

Hi James, Committed with the refactoring requested and the addition of a few trivial Defines and iterators that were missing due to the patch series being split. Thanks, Tamar -Original Message- From: James Greenhalgh Sent: Wednesday, January 9, 2019 3:37 PM To: Tamar Christina Cc:

RE: [PATCH 9/9][GCC][Arm] Add ACLE intrinsics for complex mutliplication and addition

Hi Kyrill, Committed with a the addition of a few trivial defines and iterators that were missing due to The patch being split. Thanks, Tamar -Original Message- From: Kyrill Tkachov Sent: Friday, December 21, 2018 11:40 AM To: Tamar Christina ; gcc-patches@gcc.gnu.org Cc: nd ;

[PATCH] tree-ssa-loop-unswitch.c: port to the dump_* API (PR tree-optimization/88763)

PR tree-optimization/88763 reports difficulties in getting useful information from the log of tree-ssa-loop-unswitch.c. As work towards improving this, this patch eliminates all uses of dump_file from that source file, in favor of the dump API (to support -fopt-info* and

[Committed] PR fortran/88376 -- remove assert()

I've committed the attached patch as obvious. 2019-01-09 Steven G. Kargl PR fortran/88376 * resolve.c (is_illegal_recursion): Remove an assert(). 2019-01-09 Steven G. Kargl PR fortran/88376 * gfortran.dg/pr88376.f90: New test. -- Steve Index: gcc/fortran/resolve.c

[PATCH] PR fortran/86322 -- Enforce F2018:C877

The attached patche fixes the PR. gfortran was not enforcing F2018:C877 and would ICE. Tested on x86_64-*-freebsd. Ok to commit? 2019-01-09 Steven G. Kargl PR fortran/86322 * decl.c (top_var_list): Set locus of expr. (gfc_match_data): Detect pointer on non-rightmost part-refs.

Re: [Patch 4/4][Aarch64] v2: Implement Aarch64 SIMD ABI

On Wed, 2019-01-09 at 10:00 +, Richard Sandiford wrote: Thanks for the quick turnaround on the comments Richard. Here is a new version where I tried to address all the issues you raised. One thing I noticed is that I think your calls_have_same_clobbers_p function only works if, when

Re: Go patch committed: Use build_variant_type_copy, not build_distinct_type_copy

On Thu, Jun 28, 2018 at 10:46 AM Ian Lance Taylor wrote: > > This patch to the Go frontend changes set_placeholder_struct_type to > use build_variant_type_copy rather than build_distinct_type_copy. > This is for PR 86343, which noted that the DECL_CONTEXT of the fields > in the copy were pointing

Re: ISO_Fortran_binding patch

Hi Thomas, Aaaah! Light bulb moment - I was looking in the $PREFIX/include directory. For whatever reason, mine does not appear in lib64 but in lib. OK, that will have to do for now because the patch is blocking my tree for a number of other things. I'll fix Bernhard's nit and commit on

[PATCH, libphobos] Committed remove or update of library deprecations

This patch merges the phobos library with upstream b022e552a. Removes or updates the removal date of all deprecations in phobos. Many of the marked functions have passed their end dates, and are now absent in upstream. Bootstrapped and tested on x86_64-linux-gnu. Committed to trunk as r267788

[PATCH] Move PR84877 fix elsewhere (PR bootstrap/88450)

Hi! The r266345 change breaks mingw bootstraps for quite some time. The problem is that the dynamic realignment is done IMHO way too low. The biggest problem is that when assign_stack_local_1 decides to do this dynamic_align_addr, it emits wherever it is currently expanding code about 3

Re: [PATCH][AArch64] Use Q-reg loads/stores in movmem expansion

Hi James, TImode is an integer mode so we strongly prefer using integer registers to avoid inefficient allocations using SIMD registers. We might be able to use TFmode since that prefers Q registers. However we don't support TFmode LDP/STP unless emitted explicitly like in prolog/epilog. LDP of

Re: ISO_Fortran_binding patch

On Wed, Jan 9, 2019 at 3:08 PM Thomas Koenig wrote: > > > Thanks a lot for this! Looking at what we are currently > finishing, I think we will be quite close to F2008 conformance > when gcc 9 comes out, modulo a few bugs, of course. And because ISO_Fortran_binding.h is part of Fortran 2018,

Re: ISO_Fortran_binding patch

Hi Paul, Incidentally, we need to make sure that it is distributed in the include directory. I have yet to figure out how to do that. It already does that, that was part of what I sent you :-) It's the +gfor_c_HEADERS = $(srcdir)/ISO_Fortran_binding.h +gfor_cdir =

[PATCH, i386]: Add xorsign support

Recent discussions on mailing list reminded me on this long forgotten patch... I hope it is still OK to commit it, so gcc-9 will support optimization that benefits SPEC on x86 targets. 2019-01-09 Uroš Bizjak * config/i386/i386-protos.h (ix86_expand_xorsign): New prototype.

Re: [patch, fortran] Fix PR 68426, simplification of SPREAD

On Wed, Jan 09, 2019 at 12:11:12AM +0100, Thomas Koenig wrote: > > the attached patch fixes the PR by simpliy having gfc_simplify_spread > also do its job when there's an EXPR_STRUCTURE. The code to correctly > handle that case was already in place, it just was not run for that > case. > >

Re: Remove overall growth from badness metrics

>>> >>> Those are sizes of libxul, which is the largest library of Firefox. >>> PGO is profile guided optimization. >> >> Okay. I see. >> >> looks like for LTO, the code size increase with profiling is much smaller >> than >> that without profiling when growth is increased from 20% to 40%.

Re: [patch, rfa] Fix PR other/16615, change "can not" to "cannot" throughout docs and code

On Tue, 8 Jan 2019, Sandra Loosemore wrote: > Here are the ChangeLogs for the new patch series. Parts 1, 2, and 3 are > mechanically generated via sed (etc). Part 4 is the hand-edited changes, > identical to part 2 of the previous series except for excluding a couple > files. Part 5 is the

[PATCH, d] Committed update copyright years of d/dmd sources

Hi, Happy belated new year, this patch updates copyright years of all d/dmd sources, which are purposefully skipped by the contrib/update-copyright.py script. Committed to trunk as r267778. -- Iain --- diff --git a/gcc/d/dmd/MERGE b/gcc/d/dmd/MERGE index bc35d4adc1f..feb65923273 100644 ---

Re: [PATCH][AArch64] Use Q-reg loads/stores in movmem expansion

On Fri, Dec 21, 2018 at 06:30:49AM -0600, Kyrill Tkachov wrote: > Hi all, > > Our movmem expansion currently emits TImode loads and stores when copying > 128-bit chunks. > This generates X-register LDP/STP sequences as these are the most preferred > registers for that mode. > > For the purpose

Re: [PATCH][RFC] Extend locations where to seach for Fortran pre-include.

On Wed, 9 Jan 2019, Joseph Myers wrote: > Also, could you clarify what, in the patch > (if that's > still the current version), > > > + add_sysrooted_hdrs_prefix (, argv[2], NULL, 0, 0, false); > > is doing (that is, examples of what

Re: [PATCH][RFC] Extend locations where to seach for Fortran pre-include.

On Wed, 9 Jan 2019, Martin Liška wrote: > Hi. > > May I please ping that Joseph. The provided patch should be applicable and > I would need help with the proper locations. I'm not clear if there is a specific question here, or a patch needing review. In

Re: [PATCH 2/2] PR libstdc++/86756 Move rest of std::filesystem to libstdc++.so

On 09/01/19 13:53 +0100, Christophe Lyon wrote: On Wed, 9 Jan 2019 at 11:11, Jonathan Wakely wrote: On 09/01/19 10:09 +, Jonathan Wakely wrote: >On 08/01/19 11:13 +0100, Christophe Lyon wrote: >>On Mon, 7 Jan 2019 at 15:14, Christophe Lyon wrote: >>> >>>On Mon, 7 Jan 2019 at 13:39,

Re: [RFC] Update Stage 4 description

On Wed, 9 Jan 2019, Paul Koning wrote: > Is there, or should there be, a distinction between primary and > non-primary platforms? While platform bugs typically require fixes in > platform-specific code, I would think we would want to stay away from > bugfixes in minor platforms during stage

Re: [PATCH][RFC] Extend locations where to seach for Fortran pre-include.

On 11/30/18 2:51 PM, Martin Liška wrote: > On 11/27/18 2:40 PM, Martin Liška wrote: >> On 11/26/18 7:44 PM, Joseph Myers wrote: >>> On Mon, 26 Nov 2018, Martin Liška wrote: >>> > I don't see how this version ensures that NATIVE_SYSTEM_HEADER_DIR is > properly sysrooted. Note there's

[C++ Patch] Fix three locations

Hi, three additional fixes along the usual lines. In the grokdeclarator changes I'm not touching the actual printing of the name, but another option would be using %qD and decl here too, thus, for cases like parse/crash43.C, where everything lives inside a namespace, we would print 'N::i'.

Re: [PATCH 6/9][GCC][AArch64] Add Armv8.3-a complex intrinsics

On Fri, Dec 21, 2018 at 11:57:55AM -0600, Tamar Christina wrote: > Hi All, > > This updated patch adds NEON intrinsics and tests for the Armv8.3-a complex > multiplication and add instructions with a rotate along the Argand plane. > > The instructions are documented in the ArmARM[1] and the

Integrated Systems Europe 2019 - Visitors List

Hello & Good Day to you! We wanted to check if you would be interested in acquiring Integrated Systems Europe 2019 (International Trade Show for Computer, Electronics, Electrical Engineering, Integrated Systems, Electronic Systems, Audiovisual and Av Industry) attendees list to increase prospect

[SPARC] Use P mode iterator in more cases

On the heels of the TLS patch, this also changes some basic patterns (almost) identical in 32-bit and 64-bit modes into patterns using the P mode iterator. Tested on SPARC/Solaris 11, applied on mainline and 8 branch. 2019-01-09 Eric Botcazou * config/sparc/sparc.md

[SPARC] Fix PR target/84010

This fixes the problematic generation of TLS addresses on 64-bit SPARC, which doesn't take into account the TLS relaxation that can be done by the linker. It can turn positive offsets to the GOT register %l7 into negative offsets to the thread register %g7 so the offsets must be computed in

Re: [PATCH, GCC, AARCH64, 5/6] Enable BTI : Add new pass for BTI.

Hi On 20/12/18 16:40, Sudakshina Das wrote: > Hi James > > On 19/12/18 3:40 PM, James Greenhalgh wrote: >> On Fri, Dec 14, 2018 at 10:09:03AM -0600, Sudakshina Das wrote: >> >> >> >>> I have updated the patch according to our discussions offline. >>> The md pattern is now split into 4 patterns

Re: Remove overall growth from badness metrics

> Looks like that our current documentation has a bug in the below: > > https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html > > > -finline-functions > Consider all functions for inlining, even if they are not declared inline. >

Re: [RFC] Update Stage 4 description

On Wed, 9 Jan 2019, Paul Koning wrote: > > > > On Jan 9, 2019, at 3:42 AM, Tom de Vries wrote: > > > > [ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ] > > > > The current formulation for the description of Stage 4 here ( > > https://gcc.gnu.org/develop.html ) is: > >

Re: [RFC] Update Stage 4 description

> On Jan 9, 2019, at 3:42 AM, Tom de Vries wrote: > > [ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ] > > The current formulation for the description of Stage 4 here ( > https://gcc.gnu.org/develop.html ) is: > ... > During this period, the only (non-documentation)

Re: [Aarch64][SVE] Add copysign and xorsign support

Hi all, On 09/01/19 12:26, Richard Sandiford wrote: Alejandro Martinez Vicente writes: > Hi, > > I updated the patch to address Wilco's comment and style issues. OK, thanks. I've committed this on Alejandro's behalf with r267764. As discussed internally, I think for GCC 10 we should

Re: [PATCH 2/2] PR libstdc++/86756 Move rest of std::filesystem to libstdc++.so

On Wed, 9 Jan 2019 at 11:11, Jonathan Wakely wrote: > > On 09/01/19 10:09 +, Jonathan Wakely wrote: > >On 08/01/19 11:13 +0100, Christophe Lyon wrote: > >>On Mon, 7 Jan 2019 at 15:14, Christophe Lyon > >>wrote: > >>> > >>>On Mon, 7 Jan 2019 at 13:39, Jonathan Wakely wrote: > > On

[PATCH, og8] Update _OPENACC macro, etc. for OpenACC 2.6

Hi, This patch updates the _OPENACC macro to 201711, indicating OpenACC 2.6 support, on the openacc-gcc-8-branch. Tested with offloading to NVPTX. I will apply shortly. Cheers, Julian commit e2ff11ceee7f1294313773d013a9d68f0d4e3c02 Author: Julian Brown Date: Wed Jan 9 03:41:04 2019 -0800

Re: [Aarch64][SVE] Add copysign and xorsign support

Alejandro Martinez Vicente writes: > Hi, > > I updated the patch to address Wilco's comment and style issues. OK, thanks. As discussed internally, I think for GCC 10 we should instead make the vectoriser replace copysign with logic ops if the target has no better implementation. This would be

RE: [Aarch64][SVE] Add copysign and xorsign support

Hi, I updated the patch to address Wilco's comment and style issues. Alejandro > -Original Message- > From: Wilco Dijkstra > Sent: 08 January 2019 16:58 > To: GCC Patches ; Alejandro Martinez Vicente > > Cc: nd ; Richard Sandiford > Subject: Re: [Aarch64][SVE] Add copysign and

Re: [PATCH] PR libstdc++/88204 disable std::complex tests

On Wed, Jan 09, 2019 at 11:14:37AM +0100, Jakub Jelinek wrote: > Or is double-double considered dead format that will hopefully soon go > away, not worth spending more time on? It won't go away soon, but I think we should treat it as legacy format. Currently, to use ieee128 you need either

Re: Question on Disable no throw for -flive-patching master option.

Honza: PING^2 On 1/2/19 12:47 PM, Martin Liška wrote: > Honza: PING > > On 12/6/18 12:16 AM, Qing Zhao wrote: >> Hi, Honza, >> >> I have one question relate to whether to disable nothrow for -flive-patching >> as following: >> >> actually, there are two passes here: >> >> 1. local nothrow pass:

Re: [PATCH] Pretty printer test fixes and improvements

On 09/01/19 10:14 +, Jonathan Wakely wrote: On 09/01/19 11:09 +0100, Christophe Lyon wrote: On Wed, 9 Jan 2019 at 00:16, Jonathan Wakely wrote: Test that StdUniquePtrPrinter correctly prints std::unique_ptr objects using the old layout, prior to the PR libstdc++/77990 changes. The

Re: [PATCH] PR libstdc++/87855 fix optional for types with non-trivial copy/move

On 08/01/19 23:00 +, Jonathan Wakely wrote: When the contained value is not trivially copy (or move) constructible the union's copy (or move) constructor will be deleted, and so the _Optional_payload delegating constructors are invalid. G++ fails to diagnose this because it incorrectly

Re: [PATCH] PR libstdc++/88204 disable std::complex tests

> On 9 Jan 2019, at 10:14, Jakub Jelinek wrote: > > On Wed, Jan 09, 2019 at 09:37:40AM +, Jonathan Wakely wrote: >> The IBM128 long double format isn't foldable in constant expressions, so >> conditionally skip the std::complex cases when they'll >> fail. >> >> PR libstdc++/88204 >>

Re: [PATCH] PR libstdc++/88204 disable std::complex tests

On Wed, Jan 09, 2019 at 09:37:40AM +, Jonathan Wakely wrote: > The IBM128 long double format isn't foldable in constant expressions, so > conditionally skip the std::complex cases when they'll > fail. > > PR libstdc++/88204 > *

Re: [PATCH] Pretty printer test fixes and improvements

On 09/01/19 11:09 +0100, Christophe Lyon wrote: On Wed, 9 Jan 2019 at 00:16, Jonathan Wakely wrote: Test that StdUniquePtrPrinter correctly prints std::unique_ptr objects using the old layout, prior to the PR libstdc++/77990 changes. The printer test for a valueless std::variant started to

Re: [PATCH 2/2] PR libstdc++/86756 Move rest of std::filesystem to libstdc++.so

On 09/01/19 10:09 +, Jonathan Wakely wrote: On 08/01/19 11:13 +0100, Christophe Lyon wrote: On Mon, 7 Jan 2019 at 15:14, Christophe Lyon wrote: On Mon, 7 Jan 2019 at 13:39, Jonathan Wakely wrote: On 07/01/19 09:48 +, Jonathan Wakely wrote: >On 07/01/19 10:24 +0100, Christophe Lyon

Re: [PATCH 2/2] PR libstdc++/86756 Move rest of std::filesystem to libstdc++.so

On 08/01/19 11:13 +0100, Christophe Lyon wrote: On Mon, 7 Jan 2019 at 15:14, Christophe Lyon wrote: On Mon, 7 Jan 2019 at 13:39, Jonathan Wakely wrote: > > On 07/01/19 09:48 +, Jonathan Wakely wrote: > >On 07/01/19 10:24 +0100, Christophe Lyon wrote: > >>Hi Jonathan > >> > >>On Sun, 6

Re: [Patch 4/4][Aarch64] v2: Implement Aarch64 SIMD ABI

Steve Ellcey writes: > /* Implement TARGET_HARD_REGNO_CALL_PART_CLOBBERED. The callee only saves > the lower 64 bits of a 128-bit register. Tell the compiler the callee > clobbers the top 64 bits when restoring the bottom 64 bits. */ > > static bool >

[PATCH] PR libstdc++/88204 disable std::complex tests

The IBM128 long double format isn't foldable in constant expressions, so conditionally skip the std::complex cases when they'll fail. PR libstdc++/88204 * testsuite/26_numerics/complex/operators/more_constexpr.cc: Do not test std::complex if long double format is IBM128.

Re: ISO_Fortran_binding patch

Hi Thomas, > Is there any particular reason why you do not want to use > > ! { dg-additional-options "-I $srcdir/../../libgfortran" } > > in the test cases, and have it only once in the source trees? I will make it so. Thanks for the reminder. > > However, I have no real strong opinion on this

[wwwdocs, committed] Update Stage 4 description

[ was: Re: [RFC] Update Stage 4 description ] On 09-01-19 09:47, Richard Biener wrote: > On Wed, 9 Jan 2019, Tom de Vries wrote: > >> [ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ] >> >> The current formulation for the description of Stage 4 here ( >>

Re: [RFC] Update Stage 4 description

On Wed, 9 Jan 2019 at 08:41, Tom de Vries wrote: > > [ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ] > > The current formulation for the description of Stage 4 here ( > https://gcc.gnu.org/develop.html ) is: > ... > During this period, the only (non-documentation) changes

Re: [RFC] Update Stage 4 description

On Wed, 9 Jan 2019, Tom de Vries wrote: > [ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ] > > The current formulation for the description of Stage 4 here ( > https://gcc.gnu.org/develop.html ) is: > ... > During this period, the only (non-documentation) changes that may

Re: [PATCH] Fix the dynamic_align_addr stuff partially (PR rtl-optimization/88331)

On Tue, 8 Jan 2019, Jakub Jelinek wrote: > Hi! > > The following patch attempts to fix one of the several issues with > the r266345 commit. assign_stack_local isn't called just during expansion, > but also during RA, at which point we can't just randomly emit insns in the > middle of nowhere

Re: [PATCH] Fix up initializer_each_zero_or_onep (PR middle-end/88758)

On Tue, 8 Jan 2019, Jakub Jelinek wrote: > Hi! > > As mentioned in the PR, if a VECTOR_CST is not VECTOR_CST_STEPPED_P, > it is sufficient to recurse just on all the encoded elt, because if > the vector has more elts than encoded, all the remaining ones are equal to > the last one. > But, if it

[RFC] Update Stage 4 description

[ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ] The current formulation for the description of Stage 4 here ( https://gcc.gnu.org/develop.html ) is: ... During this period, the only (non-documentation) changes that may be made are changes that fix regressions. Other

Fix documentation about -finline-functions

The documentation is confused in various ways depending on the active branch, although the implementation in opts.c is strictly identical on all of them: mainline: Enabled at levels `-O2', `-O3', `-Os'. Also enabled by `-fprofile-use' and `-fauto-profile'. 8 branch: Enabled at