[Bug libstdc++/77537] pair constructors do not properly SFINAE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77537 --- Comment #1 from Ville Voutilainen --- See https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01230.html

Re: [PATCH] [PR libcpp/71681] Fix handling header.gcc in subdirectories

On 09/08/2016 12:09 PM, Thomas Schwinge wrote: Hi! A few review comments: On Wed, 7 Sep 2016 20:19:20 +0300, Andris Pavenis wrote: This patch fixes handling header.gcc in subdirectories when command line option -remap has been used. (I have not yet reviewed the logic

[Bug c/77520] wrong value for extended ASCII characters in -Wformat message

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77520 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug c/77521] %qc format directive should quote non-printable characters

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77521 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[PATCH] avoid non-printable characters in diagnostics (c/77620, c/77521)

While working on the -Wformat-length pass I noticed that in some diagnostics that make use of the %qc and %qs directives GCC prints non-printable characters raw. For example, it might print a newline, corrupting the diagnostic stream (bug 77521). Some other diagnostics that try to avoid this

[PATCH] PR fortran/77506

Regression tested on x86_64-*-freebsd. OK to commit? 2016-09-08 Steven G. Kargl PR fortran/77506 * array.c (gfc_match_array_constructor): CHARACTER(len=*) cannot appear in an array constructor. 2016-09-08 Steven G. Kargl

[PATCH 6/9] df selftests

gcc/ChangeLog: * df-core.c: Include selftest.h and selftest-rtl.h. (selftest::dataflow_test::dataflow_test): New ctor. (selftest::dataflow_test::~dataflow_test): New dtor. (selftest::test_df_single_set): New function. (selftest::df_core_c_tests): New

[PATCH 5/9] Introduce class function_reader

This patch generalizes the RTL-reading capabilities so that they can be run on the host as well as the build machine. The available rtx in rtl.def changes dramatically between these two configurations, so a fair amount of #ifdef GENERATOR_FILE is required to express this. This patch introduces a

[PATCH 4/9] Expose forcibly_ggc_collect and run it after all selftests

Force a GC at the end of the selftests, to shake out GC-related issues. For example, if any GC-managed items have buggy (or missing) finalizers, this last collection will ensure that things that were failed to be finalized can be detected by valgrind. gcc/ChangeLog: * ggc-tests.c

[PATCH 0/9] RFC: selftests based on RTL dumps

The current selftest code is adequate for testing individual instructions, but most interesting passes have logic involving the interaction of multiple instructions, or require a CFG and function to be runnable. In theory we could write selftests by programatically constructing a function and CFG

[PATCH 1/9] Introduce class rtx_reader

Bundle up various global variables within gensupport.c into a class rtx_reader, with a view towards making it easier to run the code more than once in-process. gcc/ChangeLog: * genconstants.c (main): Introduce noop_reader and convert call to read_md_files to a method call.

[PATCH 8/9] final.c selftests

gcc/ChangeLog: * final.c: Include selftest.h and selftest-rtl.h. (class selftest::temp_asm_out): New subclass of selftest::named_temp_file. (selftest::temp_asm_out::temp_asm_out): New ctor. (selftest::temp_asm_out::~temp_asm_out): New dtor. (class

[PATCH 9/9] cse.c selftests

This patch uses rtl_dump_test to start building out a test suite for cse. I attempted to create a reproducer for PR 71779; however I'm not yet able to replicate the bogus cse reported there via the test case. gcc/ChangeLog: * cse.c: Include selftest.h and selftest-rtl.h.

[PATCH 7/9] combine.c selftests

gcc/ChangeLog: * combine.c: Include selftest.h and selftest-rtl.h. (try_combine): Add assertion on this_basic_block. (class selftest::combine_test): New subclass of selftest::tl_dump_test. (selftest::combine_test::combine_test): New ctor.

[PATCH 2/9] Add selftest::read_file

This is used later in the kit by the selftests for final.c gcc/ChangeLog: * selftest.c (selftest::read_file): New function. (selftest::test_read_file): New function. (selftest::selftest_c_tests): Call test_read_file. * selftest.h (selftest::read_file): New decl.

[PATCH 3/9] selftest.h: add temp_override fixture

We have a lot of global state in our code. Ideally we'd reduce the amount of such global state, but a prerequisite for sane refactoring is having automated testing in place to ensure that the refactoring doesn't break anything. However, the global state itself makes it hard to write such

[Bug libstdc++/77537] New: pair constructors do not properly SFINAE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77537 Bug ID: 77537 Summary: pair constructors do not properly SFINAE Product: gcc Version: 6.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug fortran/77505] Negative character length not treated as LEN=0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77505 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4 Severity|minor

[PATCH] PR fortran/77507

The attached patch fixes issues with using keywords with the IEEE_VALUE and C_ASSOCIATED intrinsic routines. Regression tested on x86_64-*-freebsd. OK to commit? 2016-09-08 Steven G. Kargl PR fortran/77507 * intrinsic.c (add_functions): Use correct

[Bug fortran/69514] ICE with nested array constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69514 kargl at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

gcc-6-20160908 is now available

Snapshot gcc-6-20160908 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160908/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 6 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6

[Committed] PR fortran/69514

I've committed the attached patch to trunk after completing regression testing on x86_64-*-freebsd. 2016-09-08 Steven G. Kargl PR fortran/69514 * array.c (gfc_match_array_constructor): If type-spec is present, walk the array constructor performing

[Bug fortran/69514] ICE with nested array constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69514 --- Comment #7 from kargl at gcc dot gnu.org --- Author: kargl Date: Thu Sep 8 22:33:10 2016 New Revision: 240039 URL: https://gcc.gnu.org/viewcvs?rev=240039=gcc=rev Log: 2016-09-08 Steven G. Kargl PR

Re: [PATCH] - improve sprintf buffer overflow detection (middle-end/49905)

On Thu, 8 Sep 2016, Martin Sebor wrote: > diff --git a/gcc/doc/tm.texi.in b/gcc/doc/tm.texi.in > index da133a4..4607495 100644 > --- a/gcc/doc/tm.texi.in > +++ b/gcc/doc/tm.texi.in > @@ -4081,6 +4081,13 @@ In either case, it remains possible to select > code-generation for the alternate >

Re: [PATCH] - improve sprintf buffer overflow detection (middle-end/49905)

On 09/08/2016 01:45 PM, David Malcolm wrote: On Thu, 2016-09-08 at 13:03 -0600, Martin Sebor wrote: Attached is another update to the patch to address the last round of comments and suggestions, most notably to: * implement the checking of the implementation limit of 4,095 on the

Re: [PATCH, PING] DWARF: process all TYPE_DECL nodes when iterating on scopes

On 09/07/2016 11:30 AM, Richard Biener wrote: Ok, had time to look at this issue again. I see the patch works like dwarf2out works currently with respect to DIE creation order and re-location. Thank you very much for helping me with this again! So yes, that was the intent of the patch.

Re: RFA: Small PATCH to add pow2p_hwi to hwint.h

On Thu, Sep 8, 2016 at 11:55 AM, Joseph Myers wrote: > On Thu, 8 Sep 2016, Jason Merrill wrote: > >> Various places in GCC use negate, bit-and and compare to test whether >> an integer is a power of 2, but I think it would be clearer for this >> test to be wrapped in a

[Bug tree-optimization/77536] New: Vectorizer not maintaining relationship of relative block frequencies in absence of real profile data

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77536 Bug ID: 77536 Summary: Vectorizer not maintaining relationship of relative block frequencies in absence of real profile data Product: gcc Version: 7.0 Status:

[Bug bootstrap/77512] gcc compilation stops with Arithmetic Exception

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77512 Eric Botcazou changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

Re: [PATCH] - improve sprintf buffer overflow detection (middle-end/49905)

On Thu, 2016-09-08 at 13:03 -0600, Martin Sebor wrote: > Attached is another update to the patch to address the last round > of comments and suggestions, most notably to: > > * implement the checking of the implementation limit of 4,095 on > the output of a single directive to allow for

[PATCH] ada/77535: GNAT.Perfect_Hash_Generators for non-1-based strings

This patch fixes GNAT.Perfect_Hash_Generators for strings which are not 1-based. It does this by introducing its own storage type which fixes the first index as 1. This is also a minor optimization because it avoids the need to store the index. Okay for trunk? Should I try to construct a new

Re: [PATCH] - improve sprintf buffer overflow detection (middle-end/49905)

On 09/08/2016 01:21 PM, Jeff Law wrote: On 08/24/2016 10:40 AM, Martin Sebor wrote: On 08/23/2016 05:00 PM, Joseph Myers wrote: Some observations: * Does -fprintf-return-value allow for the possibility of snprintf failing because of a memory allocation failure and so returning -1 when GCC

Re: [PATCH] - improve sprintf buffer overflow detection (middle-end/49905)

On 08/24/2016 10:40 AM, Martin Sebor wrote: On 08/23/2016 05:00 PM, Joseph Myers wrote: Some observations: * Does -fprintf-return-value allow for the possibility of snprintf failing because of a memory allocation failure and so returning -1 when GCC computed bounds on what it could return if

[Bug ada/77535] GNAT.Perfect_Hash_Generators access invalid memory with non-1-based strings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77535 Florian Weimer changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

Re: [PATCH] - improve sprintf buffer overflow detection (middle-end/49905)

On 08/24/2016 05:14 PM, Manuel López-Ibáñez wrote: I agree. The challenge is that not all the bits this depends on (the g_string_concat_db and parse_in globals defined in the front end) are available in the middle end. I've been talking to David Malcolm about how best to factor things out of

[Bug ada/77535] New: GNAT.Perfect_Hash_Generators access invalid memory with non-1-based strings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77535 Bug ID: 77535 Summary: GNAT.Perfect_Hash_Generators access invalid memory with non-1-based strings Product: gcc Version: 7.0 Status: UNCONFIRMED Severity:

[Bug fortran/77532] ICE in check_dtio_interface1, at fortran/interface.c:4622

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77532 Paul Thomas changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org ---

[Bug fortran/77534] ICE in check_dtio_arg_TKR_intent, at fortran/interface.c:4572

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77534 Paul Thomas changed: What|Removed |Added CC||pault at gcc dot gnu.org

[Bug fortran/77533] ICE in check_dtio_interface1, at fortran/interface.c:4614

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77533 Paul Thomas changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org ---

[Bug fortran/77533] ICE in check_dtio_interface1, at fortran/interface.c:4614

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77533 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug fortran/77534] ICE in check_dtio_arg_TKR_intent, at fortran/interface.c:4572

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77534 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug fortran/77534] ICE in check_dtio_arg_TKR_intent, at fortran/interface.c:4572

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77534 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org ---

[Bug fortran/77532] ICE in check_dtio_interface1, at fortran/interface.c:4622

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77532 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug fortran/77525] wrong requirement of an upper bound for an array argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77525 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug fortran/77534] New: ICE in check_dtio_arg_TKR_intent, at fortran/interface.c:4572

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77534 Bug ID: 77534 Summary: ICE in check_dtio_arg_TKR_intent, at fortran/interface.c:4572 Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/77533] ICE in check_dtio_interface1, at fortran/interface.c:4614

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77533 --- Comment #1 from Gerhard Steinmetz --- Sidenote : one message mentions a "KIND = 0". $ cat z3.f90 module m type t contains procedure :: s generic :: write(formatted) => s end

Re: [PATCH 8/9] shrink-wrap: shrink-wrapping for separate components

On 07/31/2016 07:42 PM, Segher Boessenkool wrote: Deciding what blocks should run with a certain component active so that the total cost of executing the prologues (and epilogues) is optimal, is not a computationally feasible problem. Really? It's just a dataflow problem is it not and one that

[Bug fortran/77533] New: ICE in check_dtio_interface1, at fortran/interface.c:4614

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77533 Bug ID: 77533 Summary: ICE in check_dtio_interface1, at fortran/interface.c:4614 Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/77532] New: ICE in check_dtio_interface1, at fortran/interface.c:4622

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77532 Bug ID: 77532 Summary: ICE in check_dtio_interface1, at fortran/interface.c:4622 Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal

Re: [PATCH 7/9] cprop: Leave RTX_FRAME_RELATED_P instructions alone

On 07/31/2016 07:42 PM, Segher Boessenkool wrote: Doing cprop on frame-related instructions blows up spectacularly. So don't. 2016-06-07 Segher Boessenkool * regcprop.c (copyprop_hardreg_forward_1): Don't change RTX_FRAME_RELATED_P instructions.

Re: [PATCH 4/9] regrename: Don't rename restores

On 07/31/2016 07:42 PM, Segher Boessenkool wrote: A restore is supposed to restore some certain register. Restoring it into some other register will not work. Don't. 2016-06-07 Segher Boessenkool * regrename.c (build_def_use): Invalidate chains that

Re: [PATCH 6/9] sel-sched: Don't mess with register restores

On 07/31/2016 07:42 PM, Segher Boessenkool wrote: If selective scheduling copies register restores it confuses dwarf2cfi. 2016-06-07 Segher Boessenkool * sel-sched-ir.c (init_global_and_expr_for_insn): Don't copy instructions with a

Re: [PATCH 5/9] regrename: Don't run if function was separately shrink-wrapped

On 07/31/2016 07:42 PM, Segher Boessenkool wrote: Unfortunately even after the previous patch there are still a few cases where regrename creates invalid code when used together with separate shrink-wrapping. At noreturn exits regrename thinks it can use all callee-saved registers, but that is

Re: [PATCH 3/9] dce: Don't dead-code delete separately wrapped restores

On 07/31/2016 07:42 PM, Segher Boessenkool wrote: Deleting restores (before a noreturn) that are dead confuses dwarf2cfi. 2016-06-07 Segher Boessenkool * dce.c (delete_unmarked_insns): Don't delete instructions with a REG_CFA_RESTORE note. I don't

Re: [PATCH 2/9] cfgcleanup: Don't confuse CFI when -fshrink-wrap-separate

On 07/31/2016 07:42 PM, Segher Boessenkool wrote: cfgcleanup would try to join noreturn paths with different components handled. This then fails in dwarf2cfi. 2016-06-07 Segher Boessenkool * cfgcleanup.c (outgoing_edges_match): Don't join noreturn calls

[Bug driver/77529] -fno-pie disables -fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77529 --- Comment #4 from H.J. Lu --- (In reply to Matthias Klose from comment #0) > seen with a GCC 6 configured with --enable-default-pie: > > $ gcc -E -dM - < /dev/null 2>&1|grep -i 'pi[ce]' > #define __pie__ 2 > #define __PIE__ 2 > #define

Re: [PATCH 1/9] separate shrink-wrap: New command-line flag, status flag, hooks, and doc

On 07/31/2016 07:42 PM, Segher Boessenkool wrote: This patch adds a new command-line flag "-fshrink-wrap-separate", a status flag "shrink_wrapped_separate", hooks for abstracting the target components, and documentation for all those. 2016-06-07 Segher Boessenkool

Re: [PATCH 1/9] separate shrink-wrap: New command-line flag, status flag, hooks, and doc

On 08/29/2016 03:31 AM, Bernd Schmidt wrote: On 08/01/2016 03:42 AM, Segher Boessenkool wrote: +@deftypefn {Target Hook} void TARGET_SHRINK_WRAP_EMIT_PROLOGUE_COMPONENTS (sbitmap) +Emit prologue insns for the components indicated by the parameter. +@end deftypefn + +@deftypefn {Target Hook}

Re: why do we need xtensa-config.h?

Am 08.09.2016 um 18:10 schrieb augustine.sterl...@gmail.com: > On Thu, Sep 8, 2016 at 8:14 AM, Oleksij Rempel wrote: >> Am 07.09.2016 um 18:21 schrieb augustine.sterl...@gmail.com: >>> On Tue, Sep 6, 2016 at 11:55 PM, Thomas Schwinge >>> wrote:

Re: [PATCH v2 0/9] Separate shrink-wrapping

On 08/26/2016 09:03 AM, Bernd Schmidt wrote: On 08/26/2016 04:50 PM, Segher Boessenkool wrote: The head comment starts with +/* Separate shrink-wrapping + + Instead of putting all of the prologue and epilogue in one spot, we + can put parts of it in places where those components are

Re: [PATCH v2 0/9] Separate shrink-wrapping

On 08/26/2016 10:27 AM, Segher Boessenkool wrote: On Fri, Aug 26, 2016 at 05:03:34PM +0200, Bernd Schmidt wrote: On 08/26/2016 04:50 PM, Segher Boessenkool wrote: The head comment starts with +/* Separate shrink-wrapping + + Instead of putting all of the prologue and epilogue in one spot,

Re: [PATCH v2 0/9] Separate shrink-wrapping

On 08/30/2016 06:31 AM, Michael Matz wrote: Hi, On Fri, 26 Aug 2016, Bernd Schmidt wrote: And that comment puzzles me. Surely prologue and epilogue are executed only once currently, so how does frequency come into it? Again - please provide an example. int some_global; int foo (void) { if

Re: [x86] Disable STV pass if -mstackrealign is enabled.

> What should I look for with 'svn annotate' ? "Disable STV" line 5959 of config/i386/i386.c. -- Eric Botcazou

[Bug preprocessor/71681] header.gcc file lookup is broken for -remap

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71681 --- Comment #3 from Andris Pavenis --- Patch in mailing list https://gcc.gnu.org/ml/gcc-patches/2016-09/msg00395.html

Re: why do we need xtensa-config.h?

On Thu, Sep 8, 2016 at 8:14 AM, Oleksij Rempel wrote: > Am 07.09.2016 um 18:21 schrieb augustine.sterl...@gmail.com: >> On Tue, Sep 6, 2016 at 11:55 PM, Thomas Schwinge >> wrote: >>> Hi! >>> >>> Neither do I really know anything about Xtensa, nor

Re: RFA: Small PATCH to add pow2p_hwi to hwint.h

On Thu, 8 Sep 2016, Jason Merrill wrote: > Various places in GCC use negate, bit-and and compare to test whether > an integer is a power of 2, but I think it would be clearer for this > test to be wrapped in a function. (x & -x) == x is also true for 0. Whatever the correct function semantics

Re: [PATCH][expmed.c] PR middle-end/77426 Delete duplicate condition in synth_mult

On 09/07/2016 06:59 AM, Kyrill Tkachov wrote: Hi all, The duplicate mode check in synth can just be deleted IMO. It was introduced as part of r139821 that was a much larger change introducing size/speed differentiation to the RTL midend. So I think it's just a typo/copy-pasto. Tested on

[Bug c/77530] optimization prevents excess precision from being removed with x86/amd64 long double and rounding to 53 bits

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77530 --- Comment #3 from Vincent Lefèvre --- More precisely, up to NetBSD 6, it is 53 bits (gcc70 is NetBSD 5.1). As of NetBSD 7, it is 64 bits.

[Bug c/77530] optimization prevents excess precision from being removed with x86/amd64 long double and rounding to 53 bits

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77530 --- Comment #2 from Vincent Lefèvre --- This seems to depend on the NetBSD version. The default rounding precision has changed in NetBSD 7.0: https://www.netbsd.org/changes/changes-7.0.html

[Bug c/77530] optimization prevents excess precision from being removed with x86/amd64 long double and rounding to 53 bits

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77530 --- Comment #1 from joseph at codesourcery dot com --- The x86 back end uses TARGET_96_ROUND_53_LONG_DOUBLE only for the case of 32-bit mode on DragonflyBSD and FreeBSD. From what you're saying here, it needs to do so for NetBSD as well (both

[Bug c/77531] New: __attribute__((alloc_size(1,2))) could also warn on multiplication overflow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77531 Bug ID: 77531 Summary: __attribute__((alloc_size(1,2))) could also warn on multiplication overflow Product: gcc Version: unknown Status: UNCONFIRMED Severity:

Re: [PATCH][v3] GIMPLE store merging pass

On 8 September 2016 at 10:31, Kyrill Tkachov wrote: > > On 07/09/16 20:03, Bernhard Reutner-Fischer wrote: >> >> On September 6, 2016 5:14:47 PM GMT+02:00, Kyrill Tkachov >> wrote: > Thanks, fixed all the above in my tree (will be

[Bug driver/77529] -fno-pie disables -fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77529 Markus Trippelsdorf changed: What|Removed |Added CC||hjl.tools at gmail dot com ---

Re: why do we need xtensa-config.h?

Am 07.09.2016 um 18:21 schrieb augustine.sterl...@gmail.com: > On Tue, Sep 6, 2016 at 11:55 PM, Thomas Schwinge > wrote: >> Hi! >> >> Neither do I really know anything about Xtensa, nor do I have a lot of >> experience in these parts of GCC back ends, but: > > There is a

[Bug driver/77529] -fno-pie disables -fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77529 --- Comment #2 from Markus Trippelsdorf --- Clang behaves exactly the same.

Re: RFA: Small PATCH to add pow2p_hwi to hwint.h

On Thu, Sep 08, 2016 at 08:53:26AM -0600, Jeff Law wrote: > On 09/07/2016 11:56 PM, Jason Merrill wrote: > > Various places in GCC use negate, bit-and and compare to test whether > > an integer is a power of 2, but I think it would be clearer for this > > test to be wrapped in a function. > > > >

Re: Make max_align_t respect _Float128 [version 2]

On 09/08/2016 04:56 AM, Mark Wielaard wrote: I don't think there is anything valgrind can do to detect that compw really only depends on d[0] if the result is false. valgrind (with the default --partial-loads-ok=yes) could and should do the same thing with cmpw that it already does with cmpl.

[Bug driver/77529] -fno-pie disables -fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77529 Markus Trippelsdorf changed: What|Removed |Added CC||trippels at gcc dot gnu.org ---

Re: RFA: Small PATCH to add pow2p_hwi to hwint.h

On 09/07/2016 11:56 PM, Jason Merrill wrote: Various places in GCC use negate, bit-and and compare to test whether an integer is a power of 2, but I think it would be clearer for this test to be wrapped in a function. OK for trunk? I think the canonical way we've written that is exact_log2

[Bug debug/61013] [4.9/4.10 Regression] Option parsing difference between < 4.9 and 4.9

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61013 --- Comment #17 from Jakub Jelinek --- As mentioned in PR77454, do we want to treat -gdwarf-N the same as -g (in addition to setting the dwarf version), or should it be treated just like setting of the DWARF version only if some debug info level

[Bug driver/77497] [5/6/7 Regression] Setting DWARF level and debug level together has flag-ordering-dependent results

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77497 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #1

[Bug driver/77497] [5/6/7 Regression] Setting DWARF level and debug level together has flag-ordering-dependent results

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77497 --- Comment #2 from torne at google dot com --- Ah. I can see the logic in "-g1 -g" resulting in -g2 level output (as explained in that bug), but it seems less ideal here where the second -g is only really intending to define the DWARF level -

[Bug c/77530] New: optimization prevents excess precision from being removed with x86/amd64 long double and rounding to 53 bits

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77530 Bug ID: 77530 Summary: optimization prevents excess precision from being removed with x86/amd64 long double and rounding to 53 bits Product: gcc Version: unknown

[Bug target/77476] [7 Regression] [AVX-512] illegal kmovb instruction on KNL

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77476 Jakub Jelinek changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/77527] [7 Regression] ICE: in make_decl_rtl, at varasm.c:1311 with -mstringop-strategy=libcall

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77527 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #1

Re: [x86] Disable STV pass if -mstackrealign is enabled.

On Wed, Sep 7, 2016 at 11:00 PM, Eric Botcazou wrote: >> Is there a testcase to show the problem with -mincoming-stack-boundary= >> on Linux? > > I don't know, 'svn annotate' will probably tell you. What should I look for with 'svn annotate' ? -- H.J.

[Bug driver/77529] New: -fno-pie disables -fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77529 Bug ID: 77529 Summary: -fno-pie disables -fPIC Product: gcc Version: 6.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: driver

[PATCH][AArch64] Align FP callee-saves

If the number of integer callee-saves is odd, the FP callee-saves use 8-byte aligned LDP/STP. Since 16-byte alignment may be faster on some CPUs, align the FP callee-saves to 16 bytes and use the alignment gap for the last FP callee-save when possible. Besides slightly different offsets for FP

Re: [patch, libgomp, OpenACC] Additional enter/exit data map handling

Hi! On Thu, 8 Sep 2016 19:18:30 +0800, Chung-Lin Tang wrote: > On 2016/9/6 8:11 PM, Thomas Schwinge wrote: > > On Mon, 29 Aug 2016 15:46:47 +0800, Chung-Lin Tang > > wrote: > >> this patch is a port of some changes from gomp-4_0-branch, > >>

[Bug tree-optimization/65068] Improve rewriting for address type induction variables in IVOPT

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65068 Wilco changed: What|Removed |Added CC||wdijkstr at arm dot com --- Comment #3 from

[Bug libstdc++/77528] std::queue default constructor unnecessarily creates temporary of underlying Container

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77528 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[PATCH] -fsanitize=thread fixes (PR sanitizer/68260, take 2)

On Thu, Sep 08, 2016 at 02:34:18PM +0200, Jakub Jelinek wrote: > I can split the patch into two, one dealing just with the > __atomic_clear/__atomic_test_and_set instrumentation and another for the > preexisting -fnon-call-exceptions ICEs. For the latter, one possibility > would be to error out

[Bug libstdc++/77524] Empty std::deque allocates unnecessary heap memory

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77524 --- Comment #5 from Dave Rigby --- (In reply to Jonathan Wakely from comment #4) > Please create a new bug for those container adaptors, as that can and should > be fixed for the default configuration. We'll keep this bug for the >

[Bug libstdc++/77528] New: std::queue default constructor unnecessarily creates temporary of underlying Container

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77528 Bug ID: 77528 Summary: std::queue default constructor unnecessarily creates temporary of underlying Container Product: gcc Version: 6.1.0 Status: UNCONFIRMED

Re: [PATCH] -fsanitize=thread fixes (PR sanitizer/68260)

On Wed, Sep 07, 2016 at 10:40:20PM +0200, Jakub Jelinek wrote: > On Wed, Sep 07, 2016 at 09:07:45AM +0200, Richard Biener wrote: > > > @@ -493,6 +504,8 @@ instrument_builtin_call (gimple_stmt_ite > > > if (!tree_fits_uhwi_p (last_arg) > > > || memmodel_base (tree_to_uhwi

Re: Make max_align_t respect _Float128 [version 2]

On 09/08/2016 02:26 PM, Bernd Schmidt wrote: On 09/08/2016 01:21 AM, Paul Eggert wrote: Sure, attached. On Fedora 24 x86-64 (GCC 6.1.1 20160621, valgrind 3.11.0), when I compile with "gcc -O2 flexouch.c" and run with "valgrind ./a.out", valgrind complains "Invalid read of size 2". This is

[Bug libstdc++/77524] Empty std::deque allocates unnecessary heap memory

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77524 --- Comment #4 from Jonathan Wakely --- (In reply to Dave Rigby from comment #3) > As an aside, std::queue<> (defaulting to using std::deque as the underlying > Container) suffers from a similar issue - I see 4 allocations for an empty >

Re: Make max_align_t respect _Float128 [version 2]

On 09/08/2016 01:21 AM, Paul Eggert wrote: Sure, attached. On Fedora 24 x86-64 (GCC 6.1.1 20160621, valgrind 3.11.0), when I compile with "gcc -O2 flexouch.c" and run with "valgrind ./a.out", valgrind complains "Invalid read of size 2". This is because GCC compiles "p->d[0] == 2 && p->d[1] ==

[committed] Fix ICE during fortran !$omp atomic write expansion (PR fortran/77500)

Hi! expr2 for atomic write or swap is not something we want to take appart, we just want to expand it as an rvalue as is, so we shouldn't be skipping its conversions. And, for the other cases, the patch adds function.isym check so that we don't ICE if there is a call to an external function

[committed] Fix ICE with safelen(0) in fortran (PR fortran/77516)

Hi! This patch fixes ICE on safelen(0). Not adding a warning for this in the FE, as it has been added already on gomp-4_5-branch, so when it is merged, the testcase will just need to be adjusted for the added warning. Tested on x86_64-linux, committed to trunk so far. 2016-09-08 Jakub Jelinek

  1   2   >