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: [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 se

[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 [...] * Makefile.in: Regenerated. * aclocal.m4: Likew

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 can't use PKG_CHEC

[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. * config.h.

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 2016 + > > Remove build dependence on HS

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):

[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 f(long

[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 perf

[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 PR

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 =

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 resul

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. -- Jo

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 gdb/dwarf2-

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 dur

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 that for > > var-trac

[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 cross-compile

[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 (format_integer): Don't handle

[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 (loc_descr_plus_const): For negativ

[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 when

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 Saturday 26 November 2016 12:11 AM, Denis Chertykov wrot

[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 app

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 t

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] [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 >

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: [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 > > I have noticed that

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 impossible to link any C++ pr

Re: Go patch committed: Merge to gccgo branch

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

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 t

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 actually available. Theref

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 just

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 >>> that contains an unresolved reference to al

[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 (

[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 without

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 M

[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, &res); return res; } Current trunk at -O2 generates f

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 produces an unusable libstdc++.so that contains an u

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 stumbled upon undesirable bb copyi

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 remov

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 wrote: > > Hi, > >>>

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 bootstrapp

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 (const

[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 Boessenko

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" LD="/home/am

[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 th

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

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 i

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 has

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 st

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 o

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 use a variadic catch-all for the false-cases. *

[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 uns

Re: Go patch committed: Merge to gccgo branch

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

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 e

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. -- Markus

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 a proper trait. Does this patch fix >> the probl

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 hiding in a basement so as to av

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 &spec, >*pprec = prec; > } > > +/* With the range [*ARGMIN, *ARGMAX] of an integer directive's actual > + argument, due to the conversion from either *ARGMIN

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 wrote: > > On 30 November 2016 at 20:00,

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

On Wed, Nov 30, 2016 at 06:14:14PM -0700, Martin Sebor wrote: > 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?

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

<    1   2