[PATCH v2] Add no_tail_call attribute

On Mon, May 29, 2017 at 8:14 AM, Yuri Gribov wrote: > Hi all, > > As discussed in > https://sourceware.org/ml/libc-alpha/2017-01/msg00455.html , some > libdl functions rely on return address to figure out the calling > DSO and then use this information in computation (e.g.

Re: [C++ PATCH] namespace stat hack representation

On Mon, May 29, 2017 at 8:11 AM, Nathan Sidwell wrote: > Currently bindings have two slots, a 'value' slot for the regular binding, > and a 'type' slot for the struct name binding, which is only used when the > value slot is holding something else. for instance: > > struct foo

Re: [PATCH] gcc: xtensa: fix fprintf format specifiers

On Mon, May 29, 2017 at 9:08 AM, augustine.sterl...@gmail.com wrote: > On Mon, May 29, 2017 at 4:11 AM, Max Filippov wrote: >> HOST_WIDE_INT may not be long as assumed in print_operand and >> xtensa_emit_call. Use

Re: [PATCH] gcc: xtensa: fix unused parameter warning

On Mon, May 29, 2017 at 9:08 AM, augustine.sterl...@gmail.com wrote: > On Mon, May 29, 2017 at 4:11 AM, Max Filippov wrote: >> 2017-05-28 Max Filippov >> gcc/ >> * config/xtensa/xtensa.c

Restore documentation of --enable-sjlj-exceptions

It had wrongly been put in the Java-specific section of doc/install.texi so was removed when the entire section was removed. Fixed thusly on the mainline and 7 branch (and entry moved on the 6 and 5 branches for good measure). Tested on x86_64-suse-linux, applied on all active branches.

Re: [libcc1] add support for C++

On 05/29/2017 04:21 PM, Alexandre Oliva wrote: Here's what I'm checking in, trunk and gcc-7-branch. Regstrapped on x86_64-linux-gnu and i686-linux-gnu. [libcc1] drop unused field from C++ lang_identifier for gcc/cp/ChangeLog * cp-tree.h (lang_identifier): Drop oracle_looked_up,

Re: [PATCH 0/13] D: Submission of D Front End

> The upstream DMD compiler that comprises all components of the > standalone part is now implemented in D programming language itself. > However here GDC is still using the C++ implementation, it is a future > goal to switch to being a self-hosted compiler minus the GCC binding > interface

Re: Default std::vector default and move constructor

Hi It wasn't such a big deal to restore value-init of the allocator. So here is the updated patch. I used: _Bvector_impl() _GLIBCXX_NOEXCEPT_IF( noexcept(_Bit_alloc_type()) ) rather than using is_nothrow_default_constructible. Any advantage in one approach or the other ?

Re: [libcc1] add support for C++

On May 28, 2017, Alexandre Oliva wrote: > Oh, no! I put it there temporarily, very early in the project, because > I couldn't find a better place (I looked for available bits elsewhere, > and I recall I couldn't find any); at the end we moved to a hash_set > (see query_oracle

[C++ PATCH] PR c++/80891 #1 & #5

This patch addresses testcase #1 by stopping name lookup returning duplicates. We use TREE_VISITED (via LOOKUP_SEEN_P) on the underlying decls of an overload. This is better than what we used to do, which was either an O(N^2) search, or use of a hash table. Furthermore, we take advantage

Re: [patch, libgfortran] PR53029 missed optimization in internal read (without implied-do-loop)

On 05/29/2017 09:51 AM, Thomas Koenig wrote: Hi Jerry, Regression tested on x86_64. I have added a test case which will check the execution time of the loop. The previous results of the REAd were correct, just took a long time on large arrays. OK for trunk? OK. It might be good if you

Re: [PATCH] Dump function on internal errors

On Mon, 29 May 2017, Alexander Monakov wrote: > +/* This helper function is invoked from diagnostic routines prior to aborting > + due to internal compiler error. If a dump file is set up, dump the > + current function. */ > + > +void > +emergency_dump_function () > +{ > + if (!dump_file ||

Re: SSA range class and removal of VR_ANTI_RANGEs

Hi, On Wed, May 24, 2017 at 10:25:40AM +0200, Richard Biener wrote: > Well, anti-ranges are "evil" for actual working with ranges. They are nice > for optimizing the storage requirements though. > > As I'm replying late I'll add that yes, it does make a difference in memory > use. We've seen

Re: [gcn][patch] Add -mgpu option and plumb in assembler/linker

Hello Andrew, I apologize for taking so long to reply, I was traveling for two past weeks and just before that we suffered some local infrastructure issues that prevented me from working on this too. On Fri, Apr 28, 2017 at 06:06:39PM +0100, Andrew Stubbs wrote: > This patch, for the "gcn"

[C++ PATCH] PR c++80891 case #4

this fixes the 4th testcase. I'd flubbed the sense of an assert. nathan -- Nathan Sidwell 2017-05-29 Nathan Sidwell PR c++/80891 (#4) * ptree.c (cxx_print_xnode): Show internal OVERLOAD structure. * tree.c (ovl_insert, ovl_iterator_remove_node): Fix copying assert. PR

Re: [PATCH] Dump function on internal errors

On Mon, May 29, 2017 at 07:46:22PM +0300, Alexander Monakov wrote: > On Mon, 29 May 2017, Alexander Monakov wrote: > > On Mon, 29 May 2017, Jakub Jelinek wrote: > > > Also, as none of the arguments are used and we are in C++, > > > perhaps it should be > > > static void > > >

Re: [patch, libgfortran] PR53029 missed optimization in internal read (without implied-do-loop)

Hi Jerry, Regression tested on x86_64. I have added a test case which will check the execution time of the loop. The previous results of the REAd were correct, just took a long time on large arrays. OK for trunk? OK. It might be good if you followed Manfred's suggestion and turned down

Re: [PATCH] Dump function on internal errors

On Mon, 29 May 2017, Alexander Monakov wrote: > On Mon, 29 May 2017, Jakub Jelinek wrote: > > Also, as none of the arguments are used and we are in C++, > > perhaps it should be > > static void > > internal_error_function (diagnostic_context *, const char *, va_list *) > > { > > ? > > Ah, it

Re: [PATCH] Dump function on internal errors

On Mon, May 29, 2017 at 07:15:33PM +0300, Alexander Monakov wrote: > Hi, > > On Wed, 24 May 2017, Richard Biener wrote: > > current_pass might be NULL so you better do set_internal_error_hook when > > we start executing passes (I detest global singletons to do such stuff > > anyway). > > I

Re: [PATCH] Dump function on internal errors

On Mon, 29 May 2017, Jakub Jelinek wrote: > What if there is another ICE during the dumping? Won't we then > end in endless recursion? Perhaps global_dc->internal_error should > be cleared here first? Hm, no, as far as I can see existing diagnostic machinery is supposed to fully handle that.

Re: [Patch, fortran] PR35339 Optimize implied do loops in io statements

> Le 29 mai 2017 à 17:49, Nicolas Koenig a écrit : > > Hello Dominique, > > mea culpa, their was a bit confusion with the file being open in emacs > and vi at the same time. Attached is the new patch with the #define removed. > > Nicolas > Thanks for the quick fix!

Re: [PATCH] Dump function on internal errors

On Mon, May 29, 2017 at 07:15:33PM +0300, Alexander Monakov wrote: > @@ -1063,6 +1064,17 @@ open_auxiliary_file (const char *ext) >return file; > } > > +/* Auxiliary callback for the diagnostics code. */ > + > +static void > +internal_error_function (diagnostic_context *context

Re: [PATCH] Dump function on internal errors

Hi, On Wed, 24 May 2017, Richard Biener wrote: > current_pass might be NULL so you better do set_internal_error_hook when > we start executing passes (I detest global singletons to do such stuff > anyway). I think there are other problems in this patch, dump_function_to_file won't work after

Re: [PATCH] gcc: xtensa: fix fprintf format specifiers

On Mon, May 29, 2017 at 4:11 AM, Max Filippov wrote: > HOST_WIDE_INT may not be long as assumed in print_operand and > xtensa_emit_call. Use HOST_WIDE_INT_PRINT_DEC/HOST_WIDE_INT_PRINT_HEX > format strings instead of %ld/0x%lx. This fixes incorrect assembly code > generation

Re: [PATCH] gcc: xtensa: fix unused parameter warning

On Mon, May 29, 2017 at 4:11 AM, Max Filippov wrote: > 2017-05-28 Max Filippov > gcc/ > * config/xtensa/xtensa.c (xtensa_initial_elimination_offset): > Mark 'to' argument with ATTRIBUTE_UNUSED. This is ok.

Re: [Patch, fortran] PR35339 Optimize implied do loops in io statements

Hello Dominique, mea culpa, their was a bit confusion with the file being open in emacs and vi at the same time. Attached is the new patch with the #define removed. Nicolas On 05/29/2017 05:32 PM, Dominique d'Humières wrote: Hi Nicolas, Updating gfortran with your patch fails with

Re: [Patch, fortran] PR35339 Optimize implied do loops in io statements

Hi Nicolas, Updating gfortran with your patch fails with ../../work/gcc/fortran/frontend-passes.c: In function 'bool traverse_io_block(gfc_code*, bool*, gfc_code*)': ../../work/gcc/fortran/frontend-passes.c:1067:20: error: expected unqualified-id before '(' token #define swap(x, y) (x) ^=

Re: [C++ PATCH] namespace stat hack representation

On 05/29/2017 11:17 AM, Marek Polacek wrote: On Mon, May 29, 2017 at 11:11:12AM -0400, Nathan Sidwell wrote: +static tree stat_hack (tree decl = NULL_TREE, tree type = NULL_TREE) Should be static tree stat_hack (tree decl = NULL_TREE, tree type = NULL_TREE) to make it easier to grep for the

Re: [C++ PATCH] namespace stat hack representation

On Mon, May 29, 2017 at 11:11:12AM -0400, Nathan Sidwell wrote: > Currently bindings have two slots, a 'value' slot for the regular binding, > and a 'type' slot for the struct name binding, which is only used when the > value slot is holding something else. for instance: > > struct foo {...}

[C++ PATCH] namespace stat hack representation

Currently bindings have two slots, a 'value' slot for the regular binding, and a 'type' slot for the struct name binding, which is only used when the value slot is holding something else. for instance: struct foo {...} foo; The value slot will be a VAR_DECL, and the type slot an artificial

Re: [PATCH] Introduce 4-stages profiledbootstrap to get a better profile.

> On 05/25/2017 01:22 PM, Markus Trippelsdorf wrote: > > On 2017.05.25 at 11:55 +0200, Martin Liška wrote: > >> Hi. > >> > >> As I spoke about the PGO with Honza and Richi, current 3-stage is not > >> ideal for following > >> 2 reasons: > >> > >> 1) stageprofile compiler is train just on

[PATCH v7 4/4] Add gdb for or1k build

* ChangeLog: 2017-02-12 Stafford Horne * configure.ac: Remove logic adding gdb to noconfigsdirs for or1k. * configure: Regenerate. Cc: gcc-patches@gcc.gnu.org --- configure| 7 --- configure.ac | 7 --- 2 files changed, 14 deletions(-) diff

[C++ PATCH] PR 80891 #1

This patch fixes the first testcase in 80891. That was a case af a using declaration and a using directive bringing in the same function during lookup. the template specialization machinery wasn't prepared for that, and reasonably thought neither instance was more specialized. This patch

Re: [patch, libgfortran] PR53029 missed optimization in internal read (without implied-do-loop)

Am 29.05.2017 um 01:16 schrieb Jerry DeLisle: > Hi all, > > The problem here is that we never set the err return to LIBERROR_END in all > cases. For the example case we are detecting the EOF condition inside the > read_integer procedure and it gets acted on correctly at higher levels in the >

Re: [PATCH] add more detail to -Wconversion and -Woverflow (PR 80731)

On 25 May 2017 at 00:16, Martin Sebor wrote: > On 05/24/2017 11:08 AM, Joseph Myers wrote: >> >> On Wed, 17 May 2017, Martin Sebor wrote: >> >>> @@ -1036,31 +1079,76 @@ warnings_for_convert_and_check (location_t loc, >>> tree type, tree expr, >>> /* This detects cases

Re: MAINTAINERS update

On 05/27/2017 12:52 PM, Bernd Schmidt wrote: I am no longer working for Red Hat, so I've updated my email address. Also, I don't expect to be around very much in the near future, so I've removed myself as maintainer for some areas. Judging by a reply I got, I may have been too terse. No need

Re: [PATCH 2/2] DWARF: make it possible to emit debug info for declarations only

On 05/29/2017 09:50 AM, Pierre-Marie de Rodat wrote: Bootstrapped and reg-tested on x86_64-linux. Ok to commit? Thank you in advance! I just realized that I forgot to add the testcase: here it is, sorry! -- Pierre-Marie de Rodat -- { dg-options "-cargs -g -dA -margs" } -- { dg-final {

[C++ PATCH] PR c++/80891 #3

This patch fixes the 3rd testcase in 80891. Here we were squirelling away overload lookup results in template definitions, but failing to mark them as used. tsubst rightly asserted. Fixed by adding calls to lookup_mark in the relevant expr build functions. build_nt_call_vec is in the common

Re: [PING][PATCH, GCC/ARM] Only test tls-disable-literal-pool.c if target supports native TLS

On 19 May 2017 at 14:29, Prakhar Bahuguna wrote: > On 11/05/2017 14:54:37, Prakhar Bahuguna wrote: >> tls-disable-literal-pool.c should only be run if the toolchain and target >> support native thread-local storage rather than emulated TLS. This patch also >> improves

Re: [PATCH, rs6000] Fold vector absolutes in GIMPLE

On Mon, May 29, 2017 at 01:35:22PM +0200, Richard Biener wrote: > >> What's the documented behavior for vec_abs with respect to an > >argument > >> of value INT_MIN? > > > >The documentation says: > > > > "For integer vectors, the arithmetic is modular." > > This means that folding as

[C++ PATCH] PR 80891#2

This patch fixes the second case reported in 80891. We were asserting the wrong thing -- the node could well be a lookup, but it must be marked USED (otherwise there's no need to copy it). I also noticed that in marking a lookup, we were not marking the underlying overloads as used -- which

Re: [PATCH, rs6000] Fold vector absolutes in GIMPLE

On May 29, 2017 12:24:44 PM GMT+02:00, Segher Boessenkool wrote: >On Mon, May 29, 2017 at 10:32:18AM +0200, Richard Biener wrote: >> On Fri, May 26, 2017 at 7:19 PM, Will Schmidt > wrote: >> > Add support for early expansion of vector

Re: [RFC] [PATCH] Introduce configure flag --with-stage1-cflags.

> After a discussion with Richi, using adding "-O2" to STAGE1 cflags with a > recent enough compiler can significantly speed up bootstrap. Thus I'm > suggesting to introduce --with-stage1-cflags where one can provide such > options. -O1 is sufficient in my experience and far less risky than -O2

[PATCH] gcc: xtensa: fix unused parameter warning

2017-05-28 Max Filippov gcc/ * config/xtensa/xtensa.c (xtensa_initial_elimination_offset): Mark 'to' argument with ATTRIBUTE_UNUSED. --- gcc/config/xtensa/xtensa.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/config/xtensa/xtensa.c

[PATCH] gcc: xtensa: fix fprintf format specifiers

HOST_WIDE_INT may not be long as assumed in print_operand and xtensa_emit_call. Use HOST_WIDE_INT_PRINT_DEC/HOST_WIDE_INT_PRINT_HEX format strings instead of %ld/0x%lx. This fixes incorrect assembly code generation by the compiler running on armhf host. 2017-05-28 Max Filippov

Re: Optimisation of std::binary_search of the header

Respected Sir, Could you give me the contact of the standard committee which handles changes to the c++ standard. Regards, Jay Pokarna On Mon, May 29, 2017 at 2:17 PM, Tim Shen wrote: > On Mon, May 29, 2017 at 1:05 AM, jay pokarna

Re: [PATCH v8] add -fpatchable-function-entry=N,M option

Ping? Richard E., this feature will immediately benefit AArch64 backend and Linux kernel. Do you plan to review it? Thank you. On Wed, May 3, 2017 at 5:48 PM, Torsten Duwe wrote: > On Wed, Mar 01, 2017 at 01:35:52PM +, Richard Earnshaw (lists) wrote: >> >> >> >> How about

Re: [PATCH, rs6000] Fold vector absolutes in GIMPLE

On Mon, May 29, 2017 at 10:32:18AM +0200, Richard Biener wrote: > On Fri, May 26, 2017 at 7:19 PM, Will Schmidt > wrote: > > Add support for early expansion of vector absolute built-ins. > > > > Bootstraps currently running (p7,p8le,p8be). > > > > OK for trunk? > >

Re: [PATCH 0/6] Improve -fprefetch-loop-arrays in general and for AArch64 in particular

Hi Andrew, Thanks for pinging this. I've re-started the submission. On 28 May 2017 at 08:01, Andrew Pinski wrote: > On Tue, Feb 28, 2017 at 1:53 AM, Maxim Kuvyrkov > wrote: >>> On Feb 20, 2017, at 5:38 PM, Kyrill Tkachov

Re: [PATCH 5/6][AArch64] Enable -fprefetch-loop-arrays at -O3 for cores that benefit from prefetching.

On 3 February 2017 at 14:58, Maxim Kuvyrkov wrote: >> On Jan 30, 2017, at 5:50 PM, Maxim Kuvyrkov >> wrote: >> >>> On Jan 30, 2017, at 3:23 PM, Kyrill Tkachov >>> wrote: >>> >>> Hi Maxim, >>> >>> On 30/01/17

Re: [PATCH 4/6] Port prefetch configuration from aarch32 to aarch64

> On Jan 30, 2017, at 2:48 PM, Maxim Kuvyrkov wrote: > > This patch port prefetch configuration from aarch32 backend to aarch64. > There is no code-generation change from this patch. > > This patch also happens to address Kyrill's comment on Andrew's prefetching >

Backport to GCC5

Hello. There's a series of patches that I installed to GCC6 and majority of there are also related to GCC 5 branch. I'm going to install the patches. Martin >From 9cbe2ada95218219ca1de6e5d9c839509f8cd6ab Mon Sep 17 00:00:00 2001 From: marxin Date:

Re: [PATCH] Add header implementation of std::to_string for integers (PR libstdc++/71108)

> Assuming that the locale issue isn't a problem, can that be reused? The to_chars patch uses C++14 features, while to_string is C++11. If that was solved, it probably could be used. However, as far as I know, simply using to_chars in to_string would technically be suboptimal, because it needs

Re: builtin fenv functions

On Mon, May 29, 2017 at 12:09 AM, Marc Glisse wrote: > On Fri, 26 May 2017, Richard Biener wrote: > > Similarly, I > don't see div as a builtin in that file, only FILE* has special code, > but > that doesn't seem worth the trouble here. So I am only declaring

Re: [PATCH, rs6000] Fold vector absolutes in GIMPLE

On Fri, May 26, 2017 at 7:19 PM, Will Schmidt wrote: > Hi, > > Add support for early expansion of vector absolute built-ins. > > Bootstraps currently running (p7,p8le,p8be). > > OK for trunk? What's the documented behavior for vec_abs with respect to an argument of

Re: [PATCH] Add no_tail_call attribute

On Mon, May 29, 2017 at 9:14 AM, Alexander Monakov wrote: > Hi, > > On Mon, 29 May 2017, Yuri Gribov wrote: > >> Hi all, >> >> As discussed in >> https://sourceware.org/ml/libc-alpha/2017-01/msg00455.html , some >> libdl functions rely on return address to figure out the

Re: [PATCH] Add no_tail_call attribute

Hi, On Mon, 29 May 2017, Yuri Gribov wrote: > Hi all, > > As discussed in > https://sourceware.org/ml/libc-alpha/2017-01/msg00455.html , some > libdl functions rely on return address to figure out the calling > DSO and then use this information in computation (e.g. output of dlsym > depends on

Re: Optimisation of std::binary_search of the header

Respected Sir, I am sorry , for the use of wrong language in the previous mail. I wanted to convey that c++ has generalised the algorithm on various data structures , which is not required due to low performance. Could you give me the contact of the standard committee?

[PATCH 1/2] gimplify_modify_expr: avoid DECL_DEBUG_EXPR links across functions

Hello, An upcoming patch exposes a bug in gimplify_modify_expr. There, we try not to create DECL_DEBUG_EXPR links across functions, however we don't check that *FROM_P actually belongs to the current function before modifying it. This patch fixes this oversight. Bootstrapped and regtested on

[PATCH 2/2] DWARF: make it possible to emit debug info for declarations only

Hello, The DWARF back-end used to systematically ignore file-scope function and variable declarations. While this is justified in language like C/C++, where such declarations can appear in several translation units and thus bloat uselessly the debug info, this behavior is counter-productive in

[contrib, committed] check_GNU_style_lib.py: Fix trailing whitespace check

Hi, this patch fixes the trailing whitespace check in check_GNU_style_lib.py. Atm, the lines passed to the checks contain the eol char, so the trailing whitespace regexp '(\s+)$' matches for a line '123\n', which is in fact without trailing whitespace. Fixed by removing the eol char.

[contrib, committed] check_GNU_style.py: Read stdin if file argument is '-'

Hi, this patch makes check_GNU_style.py read from stdin if the file argument is '-', similar to what check_GNU_style.sh does. Committed. Thanks, - Tom check_GNU_style.py: Read stdin if file argument is '-' 2017-05-28 Tom de Vries * check_GNU_style_lib.py

[contrib, committed] check_GNU_style_lib.py: Suggest to install all missing pip3 packages at once

Hi, this patch simplifies the pip3 dependency setup for check_GNU_style_lib.py. Instead of: ... $ ./contrib/check_GNU_style.py termcolor module is missing (run: pip3 install termcolor) $ pip3 install termcolor $ ./contrib/check_GNU_style.py unidiff module is missing (run: pip3 install unidiff)

[PATCH, AArch64] Add x86 intrinsic headers to GCC AArch64 taget

Hi, Please find attached the patch that adds first set of X86 instrinsic headers to AArch64 target. The implementation is based on similar work targeted at PPC64LE. https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00550.html We are using the corresponding DejaGnu tests similar to Powerpc from

Re: [RFC, PATCH][ASAN] Implement dynamic allocas/VLAs sanitization.

On Wed, May 17, 2017 at 1:24 PM, Maxim Ostapenko wrote: > Hi, > > this patch implements dynamic allocas/VLAs sanitization in ASan. Basically, > this is implemented at compiler part in the following way: > > 1) For each __builtin_alloca{_with_align} increase its size and

[PATCH] Add no_tail_call attribute

Hi all, As discussed in https://sourceware.org/ml/libc-alpha/2017-01/msg00455.html , some libdl functions rely on return address to figure out the calling DSO and then use this information in computation (e.g. output of dlsym depends on which library called it). As reported in

[PATCH 4/4 v3][PR 67328] Optimize some masked comparisons to efficient bittest

This no longer fixes the PR but still works in some cases as demonstrated by the test. So I decided to keep it. -I 0004-Optimize-some-masked-comparisons-to-efficient-bittes.patch Description: Binary data

[PATCH 3/4 v3][PR 67328] Added bool conversion for wide_ints

0003-Added-bool-conversion-for-wide_ints.patch Description: Binary data

[PATCH 2/4 v3][PR 67328] Analyze some bit tests in VRP

This improve VRP handling for bitfield comparisons added by previous patch. -I 0002-Analyze-some-bit-tests-in-VRP.patch Description: Binary data

[PATCH 1/4 v3][PR 67328] Generate bittests in range checks if possible

Added special case to build_range_check. Fixed couple of existing tests where it changed codegen. -I 0001-Generate-bittests-in-range-checks-if-possible.patch Description: Binary data

[PATCH 0/4 v3][PR 67328] Improve bitfield range tests

Hi all, This is a follow up for my previous fix for PR 67328. My original simple addition to match.pd no longer worked with GCC 7 codebase so I instead added a special case to build_range_check. I kept match.pd pattern as it still works in some other useful cases as illustrated by