Re: [C++/78252] libiberty demangler crash with lambda (auto)

On 2016.11.30 at 14:06 -0500, Nathan Sidwell wrote: > This patch fixes a problem in libiberty's symbol demangler. With a > templated forwarding function such as std::forward, we can end up emitting > mangled function names that encode lambda information. Lambdas with auto > argument types have a

Re: [PATCH, libstdc++] Fix detection of posix_memalig for cross-builds

On 1 December 2016 at 01:18, Bernd Edlinger wrote: > On 12/01/16 00:10, Jonathan Wakely wrote: >> On 30/11/16 23:06 +0100, Christophe Lyon wrote: >>> On 30 November 2016 at 22:51, Jonathan Wakely wrote: On 30/11/16 22:32 +0100, Christophe Lyon

Re: [PATCH] handle integer overflow/wrapping in printf directives (PR 78622)

On Wed, Nov 30, 2016 at 08:26:04PM -0700, Martin Sebor wrote: > @@ -795,6 +795,43 @@ get_width_and_precision (const conversion_spec , >*pprec = prec; > } > > +/* With the range [*ARGMIN, *ARGMAX] of an integer directive's actual > + argument, due to the conversion from either *ARGMIN or

Re: [v3 PATCH] Fix testsuite failures caused by the patch implementing LWG 2534.

On 1 December 2016 at 09:14, Ville Voutilainen wrote: >> Yes it does. Thank you. > Committed as obvious-enough. Also, if this change causes one more problem I'm reverting all of it, we _are_ in stage 3 and this sort of churn is not exactly desirable. I'm currently

Re: [v3 PATCH] Fix testsuite failures caused by the patch implementing LWG 2534.

On 1 December 2016 at 08:45, Markus Trippelsdorf wrote: > On 2016.12.01 at 08:11 +0200, Ville Voutilainen wrote: >> On 1 December 2016 at 07:38, Markus Trippelsdorf >> wrote: >> > It breaks building Firefox: >> >> Sigh, when writing a trait, write

Re: [v3 PATCH] Fix testsuite failures caused by the patch implementing LWG 2534.

On 2016.12.01 at 08:11 +0200, Ville Voutilainen wrote: > On 1 December 2016 at 07:38, Markus Trippelsdorf > wrote: > > It breaks building Firefox: > > Sigh, when writing a trait, write a proper trait. Does this patch fix > the problem? Yes it does. Thank you. --

Re: [PATCH] Reenable RTL sharing verification

On Wed, Nov 30, 2016 at 1:08 PM, Jakub Jelinek wrote: > Hi! > > The http://gcc.gnu.org/ml/gcc-patches/2013-04/msg01055.html > change broke all RTL sharing verification, even with --enable-checking=rtl > we don't verify anything for the last 3.5 years. Eh, I guess "oops!" doesn't quite cover that

Re: Go patch committed: Merge to gccgo branch

Now I've merged GCC trunk revision 243094 to the gccgo branch. Ian

[RS6000] fix rtl checking internal compiler error

I'm committing this one as obvious once my powerpc64le-linux bootstrap and regression check completes. It fixes hundreds of rtl checking testsuite errors like the following: gcc.c-torture/compile/pr39943.c:6:1: internal compiler error: RTL check: expected elt 0 type 'e' or 'u', have 'E' (rtx

Re: [v3 PATCH] Fix testsuite failures caused by the patch implementing LWG 2534.

On 1 December 2016 at 07:38, Markus Trippelsdorf wrote: > It breaks building Firefox: Sigh, when writing a trait, write a proper trait. Does this patch fix the problem? 2016-12-01 Ville Voutilainen The convertible_to traits need to

libgo patch committed: Set initarchive in initsig

The library initialization code in go-libmain.c sets the C variable runtime_isarchive but failed to set the Go variable runtime.isarchive. We don't currently have a way to let C code access an unexported Go variable, but fortunately the only time the Go function initsig is called with an argument

Re: [v3 PATCH] Fix testsuite failures caused by the patch implementing LWG 2534.

On 2016.11.30 at 16:25 +, Jonathan Wakely wrote: > On 30/11/16 17:58 +0200, Ville Voutilainen wrote: > >Fix testsuite failures caused by the patch implementing LWG 2534. > >* include/std/istream (__is_convertible_to_basic_istream): > >Change the return types of __check, introduce

Re: [PATCH] avoid calling alloca(0)

What I think this tells us is that we're not at a place where we're clean. But we can incrementally get there. The warning is only catching a fairly small subset of the cases AFAICT. That's not unusual and analyzing why it didn't trigger on those cases might be useful as well. The warning

Re: [Patches] Add variant constexpr support for visit, comparisons and get

On Wed, Nov 30, 2016 at 8:27 AM, Jonathan Wakely wrote: > On 26/11/16 21:38 -0800, Tim Shen wrote: >> + template> >> struct _Uninitialized; > > > I'm still unsure that is_literal_type is the right trait here. If it's > definitely right then we should probably *not* deprecate it in C++17! No

Re: [PATCH] Fix rtl sharing bug in rs6000_frame_related (PR target/78614)

On Thu, Dec 01, 2016 at 12:36:49PM +1030, Alan Modra wrote: > On Wed, Nov 30, 2016 at 11:27:40PM +0100, Jakub Jelinek wrote: > > Markus said he has bootstrapped this patch with rtl checking on powerpc64. > > I repeated the exercise and found a stage1 bootstrap failure due to > invalid rtl sharing

[PATCH] handle integer overflow/wrapping in printf directives (PR 78622)

In the gimple-ssa-sprintf pass I made the incorrect assumption that a wider integer argument in some range [X, Y] to a narrower directive (such as int to %hhi) results in the number of bytes corresponding to the range bounded by the number of bytes resulting from formatting X and Y converted to

Re: [PATCH] Fix rtl sharing bug in rs6000_frame_related (PR target/78614)

On Wed, Nov 30, 2016 at 11:27:40PM +0100, Jakub Jelinek wrote: > Markus said he has bootstrapped this patch with rtl checking on powerpc64. I repeated the exercise and found a stage1 bootstrap failure due to invalid rtl sharing on powerpc64le-linux, using AS="/home/amodra/gnu/bin/as"

[PATCH] combine: Emit a barrier after unconditional trap (PR78607)

After an unconditional trap there should be a barrier. In most cases one is automatically inserted, but not if the trap is the final insn in the instruction stream. We need to emit one explicitly. Tested on powerpc64-linux {-m64,-m32}, committing to trunk. Segher 2016-12-01 Segher

Re: [PATCH] Fix minor nits in gimple-ssa-sprintf.c (PR tree-optimization/78586)

On 11/30/2016 12:01 PM, Jakub Jelinek wrote: Hi! This patch fixes some minor nits I've raised in the PR, more severe issues left unresolved there. Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? Thank you. One comment below. @@ -1059,7 +1048,12 @@ format_integer

Re: [PATCH] Fix rtl sharing bug in rs6000_frame_related (PR target/78614)

On Wed, Nov 30, 2016 at 11:27:40PM +0100, Jakub Jelinek wrote: > As mentioned in the PR, the rs6000_frame_related rewrite broke rtl sharing > whose --enable-checking=rtl verification has been broken for the last 3.5 > years until today. Great eh! I am very scared. > Markus said he has

Re: [PATCH, libstdc++] Fix detection of posix_memalig for cross-builds

On 12/01/16 00:10, Jonathan Wakely wrote: > On 30/11/16 23:06 +0100, Christophe Lyon wrote: >> On 30 November 2016 at 22:51, Jonathan Wakely wrote: >>> On 30/11/16 22:32 +0100, Christophe Lyon wrote: On 30 November 2016 at 20:00, Bernd Edlinger

Re: [PATCH] Fix rtl sharing bug in rs6000_frame_related (PR target/78614)

On Wed, Nov 30, 2016 at 11:27:40PM +0100, Jakub Jelinek wrote: > The last hunk just removes unnecessary condition, if the condition is not > true, we return from the function already earlier and don't do any > replacements. Yeah, that was a leftover from an earlier revision of the patch that

Re: [RFA] Handle target with no length attributes sanely in bb-reorder.c

On 11/30/2016 01:38 AM, Richard Biener wrote: On Tue, Nov 29, 2016 at 5:07 PM, Jeff Law wrote: On 11/29/2016 03:23 AM, Richard Biener wrote: On Mon, Nov 28, 2016 at 10:23 PM, Jeff Law wrote: I was digging into issues around the patches for 78120 when I

Re: [PATCH, libstdc++] Fix detection of posix_memalig for cross-builds

On 30/11/16 23:06 +0100, Christophe Lyon wrote: On 30 November 2016 at 22:51, Jonathan Wakely wrote: On 30/11/16 22:32 +0100, Christophe Lyon wrote: On 30 November 2016 at 20:00, Bernd Edlinger wrote: Hi, I noticed that a cross-compiler

[PATCH][Aarch64] Add support for overflow add and sub operations

Hi, This patch improves code generations for builtin arithmetic overflow operations for the aarch64 backend. As an example for a simple test case such as: int f (int x, int y, int *ovf) { int res; *ovf = __builtin_sadd_overflow (x, y, ); return res; } Current trunk at -O2 generates f:

Re: [PATCH] Dump probability for edges a frequency for BBs

On 11/24/2016 05:59 AM, Martin Liška wrote: On 11/24/2016 09:29 AM, Richard Biener wrote: Please guard with ! TDF_GIMPLE, otherwise the output will not be parseable with the GIMPLE FE. RIchard. Done and verified that and it provides equal dumps for -fdump*-gimple. Installed as r242837. Hi

[PATCH] Fix rtl sharing bug in rs6000_frame_related (PR target/78614)

Hi! As mentioned in the PR, the rs6000_frame_related rewrite broke rtl sharing whose --enable-checking=rtl verification has been broken for the last 3.5 years until today. The problem is that simplify_replace_rtx doesn't unshare everything, only the minimum needed to replace what is needed

[PATCH] Unset used bit in simplify_replace_* on newly copied rtxs (PR target/78614)

Hi! Instead of a simple approach to fix PR78614 (a rs6000 backend bug) by adding: pat = copy_rtx (pat); before XVECEXP (pat, ...) = simplify_replace_rtx (XVECEXP (pat, ...), x, y); because simplify_replace_rtx doesn't unshare all rtxes, just those required not to modify the original expression

Re: [PATCH, libstdc++] Fix detection of posix_memalig for cross-builds

On 30 November 2016 at 22:51, Jonathan Wakely wrote: > On 30/11/16 22:32 +0100, Christophe Lyon wrote: >> >> On 30 November 2016 at 20:00, Bernd Edlinger >> wrote: >>> >>> Hi, >>> >>> I noticed that a cross-compiler produces an unusable libstdc++.so

New Spanish PO file for 'gcc' (version 6.2.0)

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 Spanish team of translators. The file is available at: http://translationproject.org/latest/gcc/es.po (This file, 'gcc-6.2.0.es.po', has

Re: [PATCH, libstdc++] Fix detection of posix_memalig for cross-builds

On 30/11/16 22:32 +0100, Christophe Lyon wrote: On 30 November 2016 at 20:00, Bernd Edlinger wrote: Hi, I noticed that a cross-compiler produces an unusable libstdc++.so that contains an unresolved reference to aligned_alloc instead of posix_memalign, or whatever is

Re: [1/9][RFC][DWARF] Reserve three DW_OP numbers in vendor extension space

How about if instead of special DW_OP codes, you instead define a new virtual register that contains the mangled return address? If the rule for that virtual register is anything other than DW_CFA_undefined, you'd expect to find the mangled return address using that rule; otherwise, you would use

Re: Go patch committed: Merge to gccgo branch

Now I've merged GCC trunk revision 243083 to the gccgo branch. Ian

Re: [PATCH, libstdc++] Fix detection of posix_memalig for cross-builds

On 30 November 2016 at 20:00, Bernd Edlinger wrote: > Hi, > > I noticed that a cross-compiler produces an unusable libstdc++.so > that contains an unresolved reference to aligned_alloc instead of > posix_memalign, or whatever is actually available. > > Therefore it is

Re: [Fortran, Patch, PR{43366, 57117, 61337, 61376}, v1] Assign to polymorphic objects.

If I compile the test with an instrumented gfortran , I get ../../work/gcc/fortran/interface.c:2948:33: runtime error: load of value 1818451807, which is not a valid value for type ‘expr_t' Dominique > Le 30 nov. 2016 à 21:06, David Edelsohn a écrit : > > Hi, Andre > >

libgo patch committed: Print C functions in traceback

This patch to libgo prints C functions when doing a stack traceback. Since gccgo can trace back through C code as easily as Go code, we should print C functions in the traceback. This worked before https://golang.org/cl/31230 for a dumb reason. The default value for runtime.traceback_cache was,

Re: [PATCH] [PR78112] Remove the g++.dg/pr78112.C testcase

On Nov 30, 2016, at 5:04 AM, Pierre-Marie de Rodat wrote: > I recently added a testcase for PR78112's resolution. Unfortunately, > what it tests changes from one platform to another and I even get > different results for a single platform (see >

Re: [Fortran, Patch, PR{43366, 57117, 61337, 61376}, v1] Assign to polymorphic objects.

Hi, Andre I have noticed that the alloc_comp_class_5.f03 testcase fails on AIX. Annotating the testcase a little, shows that the failure is at if (any(x /= ["foo", "bar", "baz"])) call abort() write (*,*) any at the point of failure produces "foobarba" - David

Re: [PATCH, libstdc++] Fix detection of posix_memalig for cross-builds

On 30/11/16 19:00 +, Bernd Edlinger wrote: Hi, I noticed that a cross-compiler produces an unusable libstdc++.so that contains an unresolved reference to aligned_alloc instead of posix_memalign, or whatever is actually available. Therefore it is impossible to link any C++ programs against

[PATCH] Minimal reimplementation of errors.c within read-md.c

On Wed, 2016-11-30 at 17:18 +0100, Bernd Schmidt wrote: > On 11/29/2016 10:13 PM, Bernd Schmidt wrote: > > On 11/29/2016 07:53 PM, David Malcolm wrote: > > > > > Would you prefer that I went with approach (B), or is approach > > > (A) > > > acceptable? > > > > Well, I was hoping there'd be an

Re: Ping: Re: [patch, avr] Add flash size to device info and make wrap around default

2016-11-30 18:09 GMT+03:00 Georg-Johann Lay : > On 30.11.2016 07:27, Pitchumani Sivanupandi wrote: >> >> On Tuesday 29 November 2016 10:06 PM, Denis Chertykov wrote: >>> >>> 2016-11-28 10:17 GMT+03:00 Pitchumani Sivanupandi >>> : On

[C++/78252] libiberty demangler crash with lambda (auto)

This patch fixes a problem in libiberty's symbol demangler. With a templated forwarding function such as std::forward, we can end up emitting mangled function names that encode lambda information. Lambdas with auto argument types have a synthesized templated operator(), and g++ uses that

[PATCH] Fix UB in dwarf2out.c (PR debug/78587)

Hi! This patch fixes 3 spots with UB in dwarf2out.c, furthermore the first spot results in smaller/better debug info. Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? 2016-11-30 Jakub Jelinek PR debug/78587 * dwarf2out.c

[PATCH] Fix minor nits in gimple-ssa-sprintf.c (PR tree-optimization/78586)

Hi! This patch fixes some minor nits I've raised in the PR, more severe issues left unresolved there. Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? 2016-11-30 Jakub Jelinek PR tree-optimization/78586 * gimple-ssa-sprintf.c

[PATCH, libstdc++] Fix detection of posix_memalig for cross-builds

Hi, I noticed that a cross-compiler produces an unusable libstdc++.so that contains an unresolved reference to aligned_alloc instead of posix_memalign, or whatever is actually available. Therefore it is impossible to link any C++ programs against the libstdc++.so that comes with the

Re: [PATCH] Another debug info stv fix (PR rtl-optimization/78547)

On Wed, Nov 30, 2016 at 08:01:11AM +0100, Uros Bizjak wrote: > On Tue, Nov 29, 2016 at 8:44 PM, Jakub Jelinek wrote: > > Hi! > > > > The following testcase ICEs because DECL_RTL/DECL_INCOMING_RTL are adjusted > > by the stv pass through the PUT_MODE modifications, which means

Re: [PATCH] Fix x86_64 fix_debug_reg_uses (PR rtl-optimization/78575)

On Tue, Nov 29, 2016 at 03:20:08PM -0700, Jeff Law wrote: > On 11/29/2016 12:41 PM, Jakub Jelinek wrote: > >Hi! > > > >The x86_64 stv pass uses PUT_MODE to change REGs and MEMs in place to affect > >all setters and users, but that is undesirable in debug insns which are > >intentionally ignored

Re: [1/9][RFC][DWARF] Reserve three DW_OP numbers in vendor extension space

On Wed, Nov 30, 2016 at 11:15:22AM +, Jiong Wang wrote: > > Hi GDB, Binutils maintainer: > > OK on this proposal and install this patch to binutils-gdb master? > This proposal is good to GDB, as long as you add a gdbarch hook and move the code handling DW_CFA_GNU_window_save in

Re: [Patch Doc] Update documentation for __fp16 type

On Wed, 30 Nov 2016, James Greenhalgh wrote: > +@code{_Float16} type defined by ISO/IEC TS18661:3-2005 Add a space after "TS", and it's -3:2015 not :3-2005. I think the -mfp16-format documentation in invoke.texi should also be updated to reflect that it affects availability of _Float16. --

Re: [PATCH 3/3] Move data definitions from icv.c back to env.c

On Wed, Nov 30, 2016 at 08:36:27PM +0300, Alexander Monakov wrote: > env.c contains a static constructor that would initialize various global > libgomp > data such as members of gomp_global_icv. Therefore it's not ok to define them > in a separate translation unit: under static linking this

patch to fix PR77856

The following patch fixes https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77856 The bug was in a new code for invariant inheritance I added this summer. The patch was successfully bootstrapped and tested on x86-64. Committed as rev. 243038. Index: ChangeLog

[PATCH][ARM] Merge negdi2 patterns

The negdi2 patterns for ARM and Thumb-2 are duplicated because Thumb-2 doesn't support RSC with an immediate. We can however emulate RSC with zero using a shifted SBC. If we add this to subsi3_carryin the negdi patterns can be merged, simplifying things a bit (eg. if changing when to split for

[PATCH 3/3] Move data definitions from icv.c back to env.c

env.c contains a static constructor that would initialize various global libgomp data such as members of gomp_global_icv. Therefore it's not ok to define them in a separate translation unit: under static linking this results in env.o not linked in (unless an incremental link on icv.o+env.o is

[PATCH][ARM] Improve Thumb allocation order

Thumb uses a special register allocation order to increase the use of low registers. Oddly enough, LR appears before R12, which means that LR must be saved and restored even if R12 is available. Swapping R12 and LR means this simple example now uses R12 as a temporary (just like ARM): int

Re: [PATCH 2/3] Introduce LIBGOMP_OFFLOADED_ONLY macro

On Wed, Nov 30, 2016 at 08:28:05PM +0300, Alexander Monakov wrote: > Introduce LIBGOMP_OFFLOADED_ONLY macro to indicate that libgomp is being built > for an accelerator-only target. > > * configure.ac [nvptx*-*-*] (libgomp_offloaded_only): Set and use it... > (LIBGOMP_OFFLOADED_ONLY):

Re: [PATCH 1/3] libgomp: regenerate with automake-1.11.6

On Wed, Nov 30, 2016 at 08:24:40PM +0300, Alexander Monakov wrote: > A recent libgomp commit (svn rev. 242749) appears to have regenerated some > auto-files using automake-1.11.1 instead of 1.11.6: > > Author: jamborm > Date: Wed Nov 23 12:27:13

[PATCH 2/3] Introduce LIBGOMP_OFFLOADED_ONLY macro

Introduce LIBGOMP_OFFLOADED_ONLY macro to indicate that libgomp is being built for an accelerator-only target. * configure.ac [nvptx*-*-*] (libgomp_offloaded_only): Set and use it... (LIBGOMP_OFFLOADED_ONLY): ...here; new define. * configure: Regenerate. *

Re: [patch] boehm-gc removal and libobjc changes to build with an external bdw-gc

On 11/30/2016 09:53 AM, Matthias Klose wrote: On 30.11.2016 12:38, Richard Biener wrote: On Wed, Nov 30, 2016 at 12:30 PM, Matthias Klose wrote: There's one more fix needed for the case of only having the pkg-config module installed when configuring with --enable-objc-gc. We

[PATCH 1/3] libgomp: regenerate with automake-1.11.6

A recent libgomp commit (svn rev. 242749) appears to have regenerated some auto-files using automake-1.11.1 instead of 1.11.6: Author: jamborm Date: Wed Nov 23 12:27:13 2016 + Remove build dependence on HSA run-time [...] *

Re: [PATCHv3 5/7, GCC, ARM, V8M] Handling ARMv8-M Security Extension's cmse_nonsecure_call attribute

On 30/11/16 12:05, Andre Vieira (lists) wrote: Hi, I got a bug report against the old version of this patch and fixed it here. This had to do with GCC optimizations sharing types with and without the 'cmse_nonsecure_call' attribute. The patch now no longer sets the main variant, this didn't

Re: [PATCHv2 4/7, GCC, ARM, V8M] ARMv8-M Security Extension's cmse_nonsecure_entry: clear registers

On 30/11/16 15:32, Andre Vieira (lists) wrote: On 23/11/16 11:52, Andre Vieira (lists) wrote: Hi, After some extra testing I realized there was an issue with the way we were clearing registers when returning from a cmse_nonsecure_entry function for ARMv8-M.Baseline. This patch fixes that and

Re: [libgomp] No references to env.c -> no libgomp construction

[redirecting from gcc@ to gcc-patches@ for patch submission] On Wed, 30 Nov 2016, Sebastian Huber wrote: > > On Tue, 29 Nov 2016, Sebastian Huber wrote: > > > * env.c: Split out ICV definitions into... > > > * icv.c: ...here (new file) and... > > > * icv-device.c: ...here.

Re: [PATCH 2/4] [ARC] Cleanup implementation.

* Claudiu Zissulescu [2016-11-16 11:17:59 +0100]: > gcc/ > 2016-06-30 Claudiu Zissulescu There seem to be two sets of changes here: > > * config/arc/arc-protos.h (insn_is_tls_gd_dispatch): Remove. > * config/arc/arc.c

Re: [PATCH, ARM] Further improve stack usage on sha512 (PR 77308)

On 11/30/16 13:01, Wilco Dijkstra wrote: > Bernd Edlinger wrote: >> On 11/29/16 16:06, Wilco Dijkstra wrote: >>> Bernd Edlinger wrote: >>> >>> - "TARGET_32BIT && reload_completed >>> + "TARGET_32BIT && ((!TARGET_NEON && !TARGET_IWMMXT) || reload_completed) >>> && ! (TARGET_NEON &&

Re: [patch] boehm-gc removal and libobjc changes to build with an external bdw-gc

On 30.11.2016 12:38, Richard Biener wrote: > On Wed, Nov 30, 2016 at 12:30 PM, Matthias Klose wrote: >> There's one more fix needed for the case of only having the pkg-config module >> installed when configuring with --enable-objc-gc. We can't use >> PKG_CHECK_MODULES >>

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

Hi all, In this awkward ICE we have a *load_multiple pattern that is being transformed in reload from: (insn 55 67 151 3 (parallel [ (set (reg:SI 0 r0) (mem/u/c:SI (reg/f:SI 147) [2 c+0 S4 A32])) (set (reg:SI 158 [ c+4 ]) (mem/u/c:SI

Re: [Patches] Add variant constexpr support for visit, comparisons and get

On 26/11/16 21:38 -0800, Tim Shen wrote: This 4-patch series contains the following in order: a.diff: Remove uses-allocator ctors. They are going away, and removing it reduces the maintenance burden from now on. Yay! less code. b.diff: Add constexpr support for get<> and comparisons. This

Re: [v3 PATCH] Fix testsuite failures caused by the patch implementing LWG 2534.

On 30/11/16 17:58 +0200, Ville Voutilainen wrote: Fix testsuite failures caused by the patch implementing LWG 2534. * include/std/istream (__is_convertible_to_basic_istream): Change the return types of __check, introduce stream_type. (operator>>(_Istream&&, _Tp&&)): Use

Re: [PATCH] Fix prs 78602 & 78560 on PowerPC (vec_extract/vec_sec)

On Wed, Nov 30, 2016 at 12:55:29AM -0500, Michael Meissner wrote: > I have done full bootstraps and make check with no regressions on a little > endian power8 (64-bit only), a big endian power8 (64-bit only), and a big > endian power7 (both 32-bit and 64-bit). Cann I install both patches to the >

Re: [PATCH,rs6000] Correct mode of operand 2 in vector extract half-word and word instruction patterns

On Wed, Nov 30, 2016 at 08:35:08AM -0700, Kelvin Nilsen wrote: > This patch corrects an error in a patch committed on 2016-10-18 to add > built-in function support for Power9 string operations. In that > original patch, the mode for operand 2 of the newly added vector > extract half-word and

Re: [PATCH 7/9] Add RTL-error-handling to host

On 11/29/2016 10:13 PM, Bernd Schmidt wrote: On 11/29/2016 07:53 PM, David Malcolm wrote: Would you prefer that I went with approach (B), or is approach (A) acceptable? Well, I was hoping there'd be an approach (C) where the read-rtl code uses whatever diagnostics framework that is

Re: [PATCH] combine: Convert subreg-of-lshiftrt to zero_extract properly (PR78390)

On Wed, Nov 30, 2016 at 03:40:32PM +0100, Michael Matz wrote: > Hi, > > On Wed, 30 Nov 2016, Segher Boessenkool wrote: > > > > I don't think mode-changing _extracts are valid in this context. From > > > the > > > docu: > > > > > > `(sign_extract:M LOC SIZE POS)' > > > ... > > > The

Re: PING! [PATCH, Fortran, accaf, v1] Add caf-API-calls to asynchronously handle allocatable components in derived type coarrays.

Fixed -> r243034. - Andre On Wed, 30 Nov 2016 15:53:39 +0100 Janus Weil wrote: > Hi, > > > on IRC: > > 15:28:22 dominiq: vehre: add /* FALLTHROUGH */ > > > > Done and committed as obvious as r243023. > > thanks. However, I still see these two: > > > >> >

[v3 PATCH] Fix testsuite failures caused by the patch implementing LWG 2534.

2016-11-30 Ville Voutilainen Fix testsuite failures caused by the patch implementing LWG 2534. * include/std/istream (__is_convertible_to_basic_istream): Change the return types of __check, introduce stream_type. (operator>>(_Istream&&, _Tp&&)):

[PATCH,rs6000] Correct mode of operand 2 in vector extract half-word and word instruction patterns

This patch corrects an error in a patch committed on 2016-10-18 to add built-in function support for Power9 string operations. In that original patch, the mode for operand 2 of the newly added vector extract half-word and full-word instruction patterns was described as V16QI, even though those

Re: [PATCHv2 4/7, GCC, ARM, V8M] ARMv8-M Security Extension's cmse_nonsecure_entry: clear registers

On 23/11/16 11:52, Andre Vieira (lists) wrote: > Hi, > > After some extra testing I realized there was an issue with the way we > were clearing registers when returning from a cmse_nonsecure_entry > function for ARMv8-M.Baseline. This patch fixes that and changes the > testcase to catch the

Re: [PATCH GCC]Simplify (cond (cmp (convert? x) c1) (op x c2) c3) -> (op (minmax x c1) c2)

On Fri, Nov 18, 2016 at 5:53 PM, Bin Cheng wrote: > Hi, > This is a rework of https://gcc.gnu.org/ml/gcc-patches/2016-10/msg02007.html. > Though review comments suggested it could be merged with last kind > simplification > of fold_cond_expr_with_comparison, it's not really

Re: Ping: Re: [patch, avr] Add flash size to device info and make wrap around default

On 30.11.2016 07:27, Pitchumani Sivanupandi wrote: On Tuesday 29 November 2016 10:06 PM, Denis Chertykov wrote: 2016-11-28 10:17 GMT+03:00 Pitchumani Sivanupandi : On Saturday 26 November 2016 12:11 AM, Denis Chertykov wrote: I'm sorry for delay. I have

Re: [v3 PATCH] LWG 2766, LWG 2749

On 26/11/16 14:47 +0200, Ville Voutilainen wrote: Updated patches attached, and tested with the full testsuite on Linux-PPC64. Both patches are OK for trunk with the minor tweaks noted below. Thanks. diff --git a/libstdc++-v3/include/bits/stl_pair.h b/libstdc++-v3/include/bits/stl_pair.h

Re: [v3 PATCH] Implement LWG 2534, Constrain rvalue stream operators.

I believe that this broke g++.old-deja/g++.law/ctors10.C invalid initialization of reference of type 'Klasse::Err&' from expression of type 'std::basic_ostream::__ostream_type {aka std::basic_ostream} - David

Re: [v3 PATCH] Implement LWG 2534, Constrain rvalue stream operators.

On 30 November 2016 at 16:59, David Edelsohn wrote: > I believe that this broke g++.old-deja/g++.law/ctors10.C > > invalid initialization of reference of type 'Klasse::Err&' from > expression of type 'std::basic_ostream::__ostream_type {aka > std::basic_ostream} I'll take a

Re: PING! [PATCH, Fortran, accaf, v1] Add caf-API-calls to asynchronously handle allocatable components in derived type coarrays.

Hi, > on IRC: > 15:28:22 dominiq: vehre: add /* FALLTHROUGH */ > > Done and committed as obvious as r243023. thanks. However, I still see these two: >> > /home/jweil/gcc/gcc7/trunk/libgfortran/caf/single.c: In function >> > ‘_gfortran_caf_get_by_ref’: >> >

[Patch Doc] Update documentation for __fp16 type

Hi, Documentation for __fp16 seems to have drifted out of line with compiler behaviour over time. This patch tries to fix that up, documenting AArch64 support and removing comments on restrictions on using the __fp16 type for arguments and return types. OK? Thanks, James --- 2016-11-30

Re: [PATCH] Partial solution to LWG 523

On 30/11/16 13:03 +, Jonathan Wakely wrote: On 26/11/16 16:27 -0800, Tim Shen wrote: diff --git a/libstdc++-v3/include/bits/shared_ptr_base.h b/libstdc++-v3/include/bits/shared_ptr_base.h index 953aa87..2fb70b7 100644 --- a/libstdc++-v3/include/bits/shared_ptr_base.h +++

Re: [PATCH] combine: Convert subreg-of-lshiftrt to zero_extract properly (PR78390)

Hi, On Wed, 30 Nov 2016, Segher Boessenkool wrote: > > I don't think mode-changing _extracts are valid in this context. From the > > docu: > > > > `(sign_extract:M LOC SIZE POS)' > > ... > > The mode M is the same as the mode that would be used for LOC if > > it were a register.

[PATCH,libstdc++] xfail operator new on AIX

AIX shared libraries do not allow overriding and interposition of symbols by default, which is used to override operators, such as operator new (and operator delete) in C++. Four libstdc++ testcases rely on this behavior and fail on AIX. Jonathan and I have decided to XFAIL the testcases to

[Patch doc] Document _Float16 availability on ARM/AArch64

Hi, As subject - update extend.texi to mention availability of _Float16 types on ARM and AArch64. OK? Thanks, James --- 2016-11-30 James Greenhalgh * doc/extend.texi (Floating Types): Document availability of _Float16 on ARM/AArch64. diff --git

Re: PING! [PATCH, Fortran, accaf, v1] Add caf-API-calls to asynchronously handle allocatable components in derived type coarrays.

Hi all, on IRC: 15:28:22 dominiq: vehre: add /* FALLTHROUGH */ Done and committed as obvious as r243023. - Andre On Wed, 30 Nov 2016 15:22:46 +0100 Andre Vehreschild wrote: > Janus, > > those fallthroughs are fully intentional and each and everyone is documented. > When you

Re: PING! [PATCH, Fortran, accaf, v1] Add caf-API-calls to asynchronously handle allocatable components in derived type coarrays.

Janus, those fallthroughs are fully intentional and each and everyone is documented. When you can tell me a way to remove those false positive warnings I am happy to do so, when it comes at no extra costs at runtime. - Andre On Wed, 30 Nov 2016 14:48:38 +0100 Janus Weil

Re: [PATCH] Fix PR78306

On Wed, 30 Nov 2016, Andrew Senkevich wrote: > 2016-11-30 11:52 GMT+03:00 Richard Biener : > > On Tue, 29 Nov 2016, Jeff Law wrote: > > > >> On 11/29/2016 12:47 AM, Richard Biener wrote: > >> > > Balaji added this check explicitly. There should be tests in the > >> > >

Re: [PATCH] combine: Convert subreg-of-lshiftrt to zero_extract properly (PR78390)

On Wed, Nov 30, 2016 at 02:43:12PM +0100, Michael Matz wrote: > > Shouldn't this be simply > > > > ... > > (ior:SI (zero_extract:SI (reg:DI) (16) (0))) > > ... > > I don't think mode-changing _extracts are valid in this context. From the > docu: > > `(sign_extract:M LOC SIZE POS)' >

Re: [PATCH PR78574]Fix infinite recursion in find_deriving_biv_for_expr

On Wed, Nov 30, 2016 at 2:54 PM, Bin Cheng wrote: > Hi, > Loop header PHI defining IV(biv) may not be identified as biv because its > increment statement is in (irreducible) inner loop. Function > find_deriving_biv_for_expr doesn't take this into consideration and runs into

Re: [PATCH][AArch64] Separate shrink wrapping hooks implementation

On 29/11/16 20:29, Segher Boessenkool wrote: Hi James, Kyrill, On Tue, Nov 29, 2016 at 10:57:33AM +, James Greenhalgh wrote: +static sbitmap +aarch64_components_for_bb (basic_block bb) +{ + bitmap in = DF_LIVE_IN (bb); + bitmap gen = _LIVE_BB_INFO (bb)->gen; + bitmap kill =

[PATCH PR78574]Fix infinite recursion in find_deriving_biv_for_expr

Hi, Loop header PHI defining IV(biv) may not be identified as biv because its increment statement is in (irreducible) inner loop. Function find_deriving_biv_for_expr doesn't take this into consideration and runs into infinite recursion. The patch fixes this issue by skipping such loop header

Re: [PATCH] ira: Don't substitute into TRAP_IF insns (PR78610)

On Wed, Nov 30, 2016 at 05:54:58AM -0700, Jeff Law wrote: > Funny how you speculated there could be these issues hiding in the > weeds, then just a few days later, one crawls out. Two (there is PR78607 as well). Although that one seems related to the combine one. All the same reporter, it's

Re: PING! [PATCH, Fortran, accaf, v1] Add caf-API-calls to asynchronously handle allocatable components in derived type coarrays.

Hi Andre, after your commit I see several warnings when compiling libgfortran (see below). Could you please fix those (if possible)? Thanks, Janus /home/jweil/gcc/gcc7/trunk/libgfortran/caf/single.c: In function ‘_gfortran_caf_is_present’:

Re: [PATCH] combine: Convert subreg-of-lshiftrt to zero_extract properly (PR78390)

Hi, On Wed, 30 Nov 2016, Dominik Vogt wrote: > On Wed, Nov 23, 2016 at 02:22:07PM +, Segher Boessenkool wrote: > > r242414, for PR77881, introduces some bugs (PR78390, PR78438, PR78477). > > It all has the same root cause: that patch makes combine convert every > > lowpart subreg of a

Re: [PATCH] ira: Don't substitute into TRAP_IF insns (PR78610)

On Wed, Nov 30, 2016 at 01:52:51PM +0100, Richard Biener wrote: > On Wed, Nov 30, 2016 at 1:46 PM, Segher Boessenkool > wrote: > > In the testcase, IRA propagates a constant into a TRAP_IF insn, which > > then becomes an unconditional trap. Unconditional traps are

Re: [PATCH] combine: Convert subreg-of-lshiftrt to zero_extract properly (PR78390)

On Wed, Nov 30, 2016 at 02:12:35PM +0100, Dominik Vogt wrote: > On Wed, Nov 23, 2016 at 02:22:07PM +, Segher Boessenkool wrote: > > r242414, for PR77881, introduces some bugs (PR78390, PR78438, PR78477). > > It all has the same root cause: that patch makes combine convert every > > lowpart

Re: PING! [PATCH, Fortran, accaf, v1] Add caf-API-calls to asynchronously handle allocatable components in derived type coarrays.

Hi Paul, thanks for the review. Committed with the changes requested and the one reported by Dominique on IRC for coarray_lib_alloc_4 when compiled with -m32 as r243021. Thanks for the review and tests. Regards, Andre On Wed, 30 Nov 2016 07:49:13 +0100 Paul Richard Thomas

  1   2   >