Re: [PATCH] Clear BB_VISITED in bb-reorder

On Mon, Oct 17, 2016 at 5:26 AM, Richard Biener wrote: > > $subject, applied as obvious. I think you should do the same for the vectorizer too. I noticed that when testing the patch for loop splitting. Thanks, Andrew > > Richard. > > 2016-10-17 Richard Biener

[Bug tree-optimization/61247] vectorization fails for unsigned is used for IV but casted to int before using as the index (and then casted for internal type)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61247 Andrew Pinski changed: What|Removed |Added Keywords||missed-optimization

Re: Use FOR_ALL_BB_FN in a few more places (was: [PATCH] Clear BB_VISITED in bb-reorder)

On October 17, 2016 6:09:02 PM GMT+02:00, Thomas Schwinge wrote: >Hi! > >On Mon, 17 Oct 2016 15:17:13 +0200, Richard Biener > wrote: >> On Mon, Oct 17, 2016 at 3:12 PM, Thomas Schwinge >> wrote: >> > On Mon, 17 Oct

Re: RFC [1/3] divmod transform v2

On 18 October 2016 at 02:46, Jeff Law wrote: > On 10/15/2016 11:59 PM, Prathamesh Kulkarni wrote: >> >> This patch is mostly the same as previous one, except it drops >> targeting __udivmoddi4() because it gave undefined reference link >> error for calling __udivmoddi4() on

[Bug c++/78011] [DR325] Compiler error when initializing a member of template type where the second template argument is a typedef

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78011 Andrew Pinski changed: What|Removed |Added Keywords||rejects-valid Status|NEW

[Bug c++/52595] [DR 325] commas and non-static data member initializers don't mix

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52595 Andrew Pinski changed: What|Removed |Added CC||b.stanimirov at abv dot bg --- Comment

[Bug c++/78011] Compiler error when initializing a member of template type where the second template argument is a typedef

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78011 --- Comment #4 from Andrew Pinski --- PR 52595

[Bug c++/78011] Compiler error when initializing a member of template type where the second template argument is a typedef

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78011 --- Comment #3 from Andrew Pinski --- PR 57

[Bug c++/78011] Compiler error when initializing a member of template type where the second template argument is a typedef

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78011 --- Comment #2 from Andrew Pinski --- There is most likely a dup about this bug. (Oh and a C++ defect report; the comma is confusing things).

[Bug fortran/48298] [F03] User-Defined Derived-Type IO (DTIO)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48298 --- Comment #28 from Jerry DeLisle --- Author: jvdelisle Date: Tue Oct 18 04:14:25 2016 New Revision: 241294 URL: https://gcc.gnu.org/viewcvs?rev=241294=gcc=rev Log: 2016-10-17 Jerry DeLisle PR fortran/48298

Re: [PATCH] Fix PR77916

On 2016.10.18 at 05:13 +0200, Markus Trippelsdorf wrote: > On 2016.10.17 at 17:23 -0500, Bill Schmidt wrote: > > Hi, > > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77916 identifies a situation > > where SLSR will ICE when exposed to a cast from integer to pointer. This > > is because we

Re: [PATCH] Fix PR77916

On 2016.10.17 at 17:23 -0500, Bill Schmidt wrote: > Hi, > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77916 identifies a situation > where SLSR will ICE when exposed to a cast from integer to pointer. This > is because we try to convert a PLUS_EXPR with an addend of -1 * S into a > MINUS_EXPR

Re: [patch, gfortran] PR48298 DTIO, implement size=

On Mon, Oct 17, 2016 at 06:02:52PM -0700, Jerry DeLisle wrote: > Hi all, > > The attached patch enables the size= specifier in a READ statement to work > with > child DTIO procedures. This is accomplished by moving the size_used variable > from the dtp structure to the gfc_unit structure so

[PATCH] xtensa: add -mpreferred-stack-boundary option

2016-05-24 Max Filippov gcc/ * config/xtensa/xtensa.opt (mpreferred-stack-boundary=): New option. * config/xtensa/xtensa.h (STACK_BOUNDARY): Redefine as 64 for windowed ABI/32 for call0 ABI. (PREFERRED_STACK_BOUNDARY): New definition.

[patch, gfortran] PR48298 DTIO, implement size=

Hi all, The attached patch enables the size= specifier in a READ statement to work with child DTIO procedures. This is accomplished by moving the size_used variable from the dtp structure to the gfc_unit structure so that the accumulation of bytes during READ is carried across the procedures

[Bug fortran/77978] stop codes misinterpreted in both f2003 and f2008

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

[PATCH] xtensa: don't use unwind-dw2-fde-dip with elf targets

Define LIB2ADDEH_XTENSA_UNWIND_DW2_FDE to unwind-dw2-fde.c in xtensa/t-elf and to unwind-dw2-fde-dip.c in xtensa/t-linux and use LIB2ADDEH_XTENSA_UNWIND_DW2_FDE in LIB2ADDEH definition. 2016-10-17 Max Filippov libgcc/ * config/xtensa/t-elf

[Bug fortran/77978] stop codes misinterpreted in both f2003 and f2008

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77978 --- Comment #6 from kargl at gcc dot gnu.org --- Author: kargl Date: Mon Oct 17 23:22:54 2016 New Revision: 241286 URL: https://gcc.gnu.org/viewcvs?rev=241286=gcc=rev Log: 2016-10-17 Steven G. Kargl Backport from

Re: [PATCH] rs6000: Fix separate shrink-wrapping for TARGET_MULTIPLE

Hi Segher, > On 17 Oct 2016, at 09:13, Segher Boessenkool > wrote: > > We cannot use {SAVE,REST}_MULTIPLE and separate shrink-wrapping together, > not without checking when actually emitting the prologue/epilogue that the > registers to save/restore are actually

[SOLVED-ish] Question about sibling call epilogues & registers

So the core problem was my "restore multiple" insn contained a CALL insn and was a call_insn. The symbol it called is in the static section of libgcc. However, during peephole2 pass, get_call_reg_set_usage in final.c didn't find a function declaration attached to the symbol and so defaulted to

[PATCH] Remove leftover comment

Whoops. Discovered I had inadvertently left in a comment that made no sense when fixing PR77916. This patch removes it. Committed as obvious. Thanks, Bill 2016-10-17 Bill Schmidt * gimple-ssa-strength-reduction.c (record_increment): Remove

Re: [patch v2] Get rid of stack trampolines for nested functions (0/4)

> On ia64 I get this regression: > > FAIL: gcc.dg/Wtrampolines.c (test for warnings, line 31) > > Since ia64 never uses trampolines this is probably ok and the test > should be adjusted. This actually revealed a problem: the same regression should have appeared on PowerPC64/Linux (ELFv1 ABI)

[PATCH] Fix PR77916

Hi, https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77916 identifies a situation where SLSR will ICE when exposed to a cast from integer to pointer. This is because we try to convert a PLUS_EXPR with an addend of -1 * S into a MINUS_EXPR with a subtrahend of S, but the base operand is unexpectedly

[Bug tree-optimization/77916] [6/7 Regression] ICE in verify_gimple_in_cfg: invalid (pointer) operands to plus/minus

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77916 --- Comment #4 from Bill Schmidt --- Author: wschmidt Date: Mon Oct 17 22:08:56 2016 New Revision: 241281 URL: https://gcc.gnu.org/viewcvs?rev=241281=gcc=rev Log: [gcc] 2016-10-17 Bill Schmidt PR

Re: [PATCH] fix outstanding -Wformat-length failures (pr77735 et al.)

On 10/17/2016 01:11 PM, Jeff Law wrote: On 10/02/2016 02:10 PM, Martin Sebor wrote: The attached patch fixes a number of outstanding test failures and ILP32-related bugs in the gimple-ssa-sprintf pattch pointed out in bug 77676 and 77735). The patch also fixes c_strlen to correctly handle

[PATCH] DWARF5 DW_FORM_implicit_const support

Hi! This patch starts using DW_FORM_implicit_const (new in DWARF5), though only for cases where the constants are the same among all DIEs with the same abbreviation (and only for abbrevs used only in the main compilation unit, because right now we don't give all DIEs abbreviations first before

Re: [PATCH] PR77895: DWARF: Emit DW_AT_comp_dir in all cases, even if source is an absolute path

On Oct 17, 2016, at 2:38 PM, Ximin Luo wrote: > > Mike Stump: >> On Oct 17, 2016, at 11:00 AM, Ximin Luo wrote: >>> Therefore, it is better to emit it in all circumstances, in case the reader >>> needs to know what the working >>> directory was at

[PATCH] DWARF5 DW_FORM_data16 support

Hi! DWARF5 has a new 128-bit constant class form, this patch uses it e.g. for __int128 values. Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? 2016-10-17 Jakub Jelinek * dwarf2out.c (size_of_die, value_format, output_die): Use

Re: [PATCH] PR77895: DWARF: Emit DW_AT_comp_dir in all cases, even if source is an absolute path

Mike Stump: > On Oct 17, 2016, at 11:00 AM, Ximin Luo wrote: >> Therefore, it is better to emit it in all circumstances, in case the reader >> needs to know what the working >> directory was at compile-time. > > I can't help but wonder if this would break ccache some? >

[PATCH] DWARF5 DW_TAG_call_site support

Hi! This is on top of the http://gcc.gnu.org/ml/gcc-patches/2016-10/msg01202.html patch. This is yet another GNU extension that got accepted into DWARF5, though in this case various attributes got renamed (other than just dropping GNU_ middle parts), or extra attributes have been added instead

[Bug fortran/77978] stop codes misinterpreted in both f2003 and f2008

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77978 --- Comment #5 from kargl at gcc dot gnu.org --- Author: kargl Date: Mon Oct 17 21:29:31 2016 New Revision: 241280 URL: https://gcc.gnu.org/viewcvs?rev=241280=gcc=rev Log: 2016-10-17 Steven G. Kargl PR

Re: [PATCH] PR77895: DWARF: Emit DW_AT_comp_dir in all cases, even if source is an absolute path

On Oct 17, 2016, at 11:00 AM, Ximin Luo wrote: > Therefore, it is better to emit it in all circumstances, in case the reader > needs to know what the working > directory was at compile-time. I can't help but wonder if this would break ccache some?

Re: RFC [1/3] divmod transform v2

On 10/15/2016 11:59 PM, Prathamesh Kulkarni wrote: This patch is mostly the same as previous one, except it drops targeting __udivmoddi4() because it gave undefined reference link error for calling __udivmoddi4() on aarch64-linux-gnu. It appears aarch64 has hardware insn for DImode div, so

[Bug c++/78014] -Wformat -vs- size_t

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014 --- Comment #3 from Tom Tromey --- (In reply to jos...@codesourcery.com from comment #2) > Likewise an expression where the user did "typedef size_t my_size_t;" and > then used my_size_t. And what about expressions resulting from arithmetic

Re: [PATCH] read-md.c: Move various state to within class rtx_reader (v3)

David Malcolm writes: >> I assume you didn't turn the functions above into member functions >> because they aren't primitives. OTOH it might seem inconsistent >> to have things like traverse_enum_types as member functions but >> traverse_md_constants not. > > In the

Re: [PATCH] (PR 65950) Improve predicate for exit(0);

On Wed, Sep 21, 2016 at 1:53 AM, Richard Biener wrote: > On Wed, Sep 21, 2016 at 10:45 AM, Andrew Pinski wrote: >> On Wed, Sep 21, 2016 at 4:32 PM, Richard Biener >> wrote: >>> On Wed, Sep 21, 2016 at 9:13 AM, Andrew

[Bug fortran/77978] stop codes misinterpreted in both f2003 and f2008

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77978 --- Comment #4 from kargl at gcc dot gnu.org --- Author: kargl Date: Mon Oct 17 19:57:12 2016 New Revision: 241279 URL: https://gcc.gnu.org/viewcvs?rev=241279=gcc=rev Log: 2016-10-17 Steven G. Kargl PR

[Bug c++/78014] -Wformat -vs- size_t

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014 --- Comment #2 from joseph at codesourcery dot com --- I think this is essentially the same as bug 77970 - making such warnings smarter about the case of standard typedefs. Of course an expression resulting from sizeof must be considered

[Bug c++/78014] -Wformat -vs- size_t

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014 Andrew Pinski changed: What|Removed |Added Keywords||diagnostic Severity|normal

[PATCH 7/7] make targetm.gen_ccmp{first,next} take rtx_insn **

From: Trevor Saunders gcc/ChangeLog: 2016-10-17 Trevor Saunders * ccmp.c (expand_ccmp_expr_1): Adjust. (expand_ccmp_expr): Likewise. (expand_ccmp_next): Likewise. * config/aarch64/aarch64.c

[PATCH 5/7] remove cast in delete_insn_chain

From: Trevor Saunders gcc/ChangeLog: 2016-10-17 Trevor Saunders * cfgrtl.c (delete_insn_chain): Change argument type to rtx_insn * and adjust for that. * cfgrtl.h (delete_insn_chain): Adjust prototype. ---

[PATCH 3/7] use rtx_insn * more

From: Trevor Saunders gcc/ChangeLog: 2016-10-17 Trevor Saunders * config/alpha/alpha.c (alpha_legitimize_address_1): Change variable types from rtx to rtx_insn *. (alpha_emit_xfloating_libcall): Likewise.

[PATCH 1/7] make LABEL_REF_LABEL a rtx_insn *

From: Trevor Saunders While chainging LABEL_REF_LABEL it might as well become an inline function, so that its clearer what types are involved. Unfortunately because it is still possible to use XEXP and related macros on a LABEL_REF rtx you can still set the field to

[PATCH 6/7] remove cast from prev_nonnote_insn_bb

From: Trevor Saunders gcc/ChangeLog: 2016-10-17 Trevor Saunders * emit-rtl.c (prev_nonnote_insn_bb): Change argument type to rtx_insn *. * rtl.h (prev_nonnote_insn_bb): Adjust prototype. --- gcc/emit-rtl.c | 3

[PATCH 2/7] make tablejump_p return the label as a rtx_insn *

From: Trevor Saunders gcc/ChangeLog: 2016-10-17 Trevor Saunders * cfgcleanup.c (merge_blocks_move_successor_nojumps): Adjust. (outgoing_edges_match): Likewise. (try_crossjump_to_edge): Likewise. * cfgrtl.c

[PATCH 4/7] remove cast to rtx_insn * in remove_note

From: Trevor Saunders gcc/ChangeLog: 2016-10-17 Trevor Saunders * config/rl78/rl78.c (gen-and_emit_move): Change argument type to rtx_insn *. (transcode_memory_rtx): Likewise. (move_to_acc): Likewise.

[PATCH 0/7] more rtx-insn stuff

From: Trevor Saunders Hi, Rather late (travel and then busy day job interfiered), but this includes the promised conversion of LABEL_REF_LABEL and tablejump_p to use rtx_insn *. Followed by a bit more random conversion of things to use rtx_insn *. patches

[Bug c++/78014] New: -Wformat -vs- size_t

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014 Bug ID: 78014 Summary: -Wformat -vs- size_t Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee:

Re: [Patch 3/11] Implement TARGET_C_EXCESS_PRECISION for s390

> Here is a patch implementing what I think has been discussed in this thread. > > OK? Looks good to me. Uli, do you agree with that change for S/390 or would you rather see us fixing the float_t type definition in Glibc? -Andreas-

Re: [PATCH 1/2] Fix GCC split-stack variadic argument tests

On 10/17/2016 01:12 PM, Adhemerval Zanella wrote: This test adds the expect va_end after va_start on split-stack tests. gcc/ChangeLog: * gcc/testsuite/gcc.dg/split-3.c (down): Call va_end after va_start. * gcc/testsuite/gcc.dg/split-6.c (down): Likewise. OK. Would probably

Re: [PATCH] Extend -Wint-in-bool-context to suspicious enum values (PR 77700)

On 10/08/2016 04:50 PM, Trevor Saunders wrote: On Fri, Oct 07, 2016 at 03:18:07PM +, Bernd Edlinger wrote: Hi! This extends -Wint-in-bool-context to uses of enum values in boolean context, and fixes one place where accidentally an enum value was passed to a bool parameter. I excluded enum

Re: [PATCH][2/2] Enable SSA propagator "DCE" for VRP

On 10/12/2016 01:08 AM, Richard Biener wrote: On Fri, 7 Oct 2016, Richard Biener wrote: This turns the switch (which also requires propagating into ASSERT_EXPRs, otherwise those will end up with released SSA names eventually). A [3/2] would be to let ASSERT_EXPRs be removed by the propagator

[Bug c++/77656] 64-bit integral template parameter gets incorrectly sized as 32-bits

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77656 --- Comment #2 from Jason Merrill --- (In reply to Jakub Jelinek from comment #1) > Perhaps tsubst of TEMPLATE_PARM_INDEX instead of just > return convert_from_reference (unshare_expr (arg)); > also convert it to the TEMPLATE_PARM_INDEX's type

Re: [PATCH, C++] Warn on redefinition of builtin functions (PR c++/71973)

On 10/17/16 20:05, Joseph Myers wrote: > On Sun, 16 Oct 2016, Bernd Edlinger wrote: > >> Second, the declaration in the glibc header files simply look wrong, >> because the type of argv, and envp is "char *const *" while the >> builtin function wants "const char**", thus only the array of char* >>

[PATCH v3 2/2] aarch64: Add split-stack initial support

From: Adhemerval Zanella Changes from previous version: * Add missing new function comments; * Using gen_rtx_fmt_ee instead of gen_rtx_IF_THEN_ELSE to create conditional jumps; * Some typos and withspace issues. -- This patch adds the split-stack support

[PATCH 1/2] Fix GCC split-stack variadic argument tests

This test adds the expect va_end after va_start on split-stack tests. gcc/ChangeLog: * gcc/testsuite/gcc.dg/split-3.c (down): Call va_end after va_start. * gcc/testsuite/gcc.dg/split-6.c (down): Likewise. --- gcc/ChangeLog | 5 +

Re: PATCH to tidy up code in c-warn.c

On 10/16/2016 04:53 AM, Marek Polacek wrote: Found when looking at something else. find_array_ref_with_const_idx_r would uselessly keep on looking for other array refs with constant indices, even though finding one is enough. So return when something is found, instead of just ignoring the

Re: [PATCH] fix outstanding -Wformat-length failures (pr77735 et al.)

On 10/02/2016 02:10 PM, Martin Sebor wrote: The attached patch fixes a number of outstanding test failures and ILP32-related bugs in the gimple-ssa-sprintf pattch pointed out in bug 77676 and 77735). The patch also fixes c_strlen to correctly handle wide strings (previously it accepted them but

Re: Who played with the GCC Bugzilla git repo?

Frédéric Buclin writes: > Someone played with the GCC Bugzilla git repo last week with no real reason: > Author: root > Date: Fri Oct 7 15:28:43 2016 + > snap-data > [...] That was little old me, with the reason being to conserve local changes with

Re: [PATCH] AIX symbol encoding

Hi David, On Mon, Oct 17, 2016 at 09:54:35AM -0400, David Edelsohn wrote: > This patch shifts earlier the point during compilation where the > rs6000 backend adds decoration to symbols: to encode_section_info. > - /* Currently C++ toc references to vtables can be emitted before it > - is

[Bug libstdc++/77987] [6/7 Regression] unique_ptr<T[]> reset rejects cv-compatible pointers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77987 Jonathan Wakely changed: What|Removed |Added Status|ASSIGNED|RESOLVED Known to work|

[Bug libstdc++/77987] unique_ptr<T[]> reset rejects cv-compatible pointers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77987 --- Comment #4 from Jonathan Wakely --- Author: redi Date: Mon Oct 17 18:21:26 2016 New Revision: 241276 URL: https://gcc.gnu.org/viewcvs?rev=241276=gcc=rev Log: PR77987 Fix unique_ptr::reset(U) for T != U PR libstdc++/77987

Re: [PATCH AArch64]Penalize vector cost for large loops with too many vect insns.

> On Oct 17, 2016, at 12:26 PM, Bin.Cheng wrote: > > On Sat, Oct 15, 2016 at 3:07 AM, kugan > wrote: >> Hi Bin, >> >> On 15/10/16 00:15, Bin Cheng wrote: >>> >>> +/* Test for likely overcommitment of vector hardware resources. If a

Re: [PATCH/AARCH64] Fix some testcases for AARCH64 ILP32

On Mon, Oct 17, 2016 at 2:55 AM, Richard Earnshaw (lists) wrote: > On 16/10/16 22:39, Andrew Pinski wrote: >> Hi, >> These testcases use long for 64bit integer which means they will >> fail with -mabi=ilp32 on aarch64. This reduces the number of failures >> down for

Re: [PATCH, C++] Warn on redefinition of builtin functions (PR c++/71973)

On Sun, 16 Oct 2016, Bernd Edlinger wrote: > Second, the declaration in the glibc header files simply look wrong, > because the type of argv, and envp is "char *const *" while the > builtin function wants "const char**", thus only the array of char* > itself is const, not the actual char stings

Re: [patch] Fix ICE on ACATS test for Aarch64 at -O

On 10/03/2016 09:45 AM, Eric Botcazou wrote: Ping: https://gcc.gnu.org/ml/gcc-patches/2016-09/msg01781.html 2016-09-26 Eric Botcazou * expmed.c (expand_shift_1): Add MAY_FAIL parameter and do not assert that the result is non-zero if it is true.

[PATCH] PR77895: DWARF: Emit DW_AT_comp_dir in all cases, even if source is an absolute path

(Please keep me on CC, I am not subscribed) In working on another patch for DW_AT_comp_dir behaviour, I tried to write a test for that other patch. This test did not work as expected - DW_AT_comp_dir was not even generated in the resulting output! But this had nothing to do with my patch so I dug

[Patch, fortran] PR61420 [5/6/7 Regression] [OOP] type-bound procedure returning a procedure pointer fails to compile

Dear All, Committed as 'obvious' on trunk as revision 241274. I will commit to 5- and 6-branches at the end of the week. Cheers Paul 2016-10-17 Paul Thomas PR fortran/61420 PR fortran/78013 * resolve.c (resolve_variable): Obtain the typespec for a

[Bug fortran/61420] [5/6/7 Regression] [OOP] type-bound procedure returning a procedure pointer fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61420 --- Comment #11 from Paul Thomas --- Author: pault Date: Mon Oct 17 17:52:05 2016 New Revision: 241274 URL: https://gcc.gnu.org/viewcvs?rev=241274=gcc=rev Log: 2016-10-17 Paul Thomas PR fortran/61420 PR

[Bug fortran/78013] unexpected 'has no IMPLICIT type' error for a type-bound function returning a procedure pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78013 --- Comment #2 from Paul Thomas --- Author: pault Date: Mon Oct 17 17:52:05 2016 New Revision: 241274 URL: https://gcc.gnu.org/viewcvs?rev=241274=gcc=rev Log: 2016-10-17 Paul Thomas PR fortran/61420 PR

[Bug target/77308] surprisingly large stack usage for sha512 on arm

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77308 --- Comment #11 from Bernd Edlinger --- Author: edlinger Date: Mon Oct 17 17:46:59 2016 New Revision: 241273 URL: https://gcc.gnu.org/viewcvs?rev=241273=gcc=rev Log: 2016-10-17 Bernd Edlinger PR

Re: [PATCH] Make -Wint-in-bool-context warn on suspicious shift ops

On 2016.10.17 at 17:30 +, Bernd Edlinger wrote: > On 10/17/16 19:11, Markus Trippelsdorf wrote: > >>> I'm seeing this warning a lot in valid low level C code for unsigned > >>> integers. And I must say it look bogus in this context. Some examples: > > > > (All these examples are from qemu

[Bug c/77992] Provide feature to initialize padding bytes to avoid information leaks

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77992 --- Comment #16 from joseph at codesourcery dot com --- Obviously any fields implicitly inserted like that must be ignored by the front ends when processing positional initializers - an initializer { 1, 2, 3 } must initialize three explicitly

Patch ping

Hi! I'd like to ping the [C++ PATCH] Fix -Wimplicit-fallthrough in templates (PR c++/77886) patch: On Sat, Oct 08, 2016 at 08:13:50AM +0200, Jakub Jelinek wrote: > 2016-10-08 Jakub Jelinek > > PR c++/77886 > * pt.c (tsubst_expr) Copy over >

[Bug c/78000] -Wimplicit-function-declaration inhibited with macro from system headers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78000 --- Comment #1 from joseph at codesourcery dot com --- As I've said before, we have to stop doing individual ad hoc fixes for bugs like this; there are too many of them. We have to work out the general principles for which warnings should or

Re: [PATCH] Make -Wint-in-bool-context warn on suspicious shift ops

On 10/17/16 19:11, Markus Trippelsdorf wrote: >>> I'm seeing this warning a lot in valid low level C code for unsigned >>> integers. And I must say it look bogus in this context. Some examples: > > (All these examples are from qemu trunk.) > >>> return ((a.high & 0x7fff) == 0x7fff) && (a.low<<1);

Re: [PATCH AArch64]Penalize vector cost for large loops with too many vect insns.

On Sat, Oct 15, 2016 at 3:07 AM, kugan wrote: > Hi Bin, > > On 15/10/16 00:15, Bin Cheng wrote: >> >> +/* Test for likely overcommitment of vector hardware resources. If a >> + loop iteration is relatively large, and too large a percentage of >> +

[Bug fortran/61420] [5/6/7 Regression] [OOP] type-bound procedure returning a procedure pointer fails to compile

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

Re: [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

On Sun, 16 Oct 2016, Shea Levy wrote: > options) and clearly have the semantics we want. Ideally we would be > able to specify something on the level of abstraction of "this directory > should be treated like you would normally treat /usr" and get > e.g. /include, /lib, frameworks on OS X, etc.

Re: [PATCH] Make -Wint-in-bool-context warn on suspicious shift ops

On 2016.10.17 at 16:51 +, Bernd Edlinger wrote: > On 10/17/16 17:23, Markus Trippelsdorf wrote: > > On 2016.09.29 at 18:52 +, Bernd Edlinger wrote: > >> On 09/29/16 20:03, Jason Merrill wrote: > >>> On Wed, Sep 28, 2016 at 12:09 PM, Bernd Edlinger > >>> wrote: >

[Bug fortran/61420] [5/6/7 Regression] [OOP] type-bound procedure returning a procedure pointer fails to compile

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

[Bug fortran/78013] unexpected 'has no IMPLICIT type' error for a type-bound function returning a procedure pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78013 Paul Thomas changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

Re: [PATCH 0/8] NVPTX offloading to NVPTX: backend patches

On Mon, 17 Oct 2016, Bernd Schmidt wrote: > On 10/14/2016 06:39 PM, Alexander Monakov wrote: > > I'm resending the patch series with backend prerequisites for OpenMP > > offloading to the NVIDIA PTX ISA. The patches are rebased on trunk. > > What's the status of the branch? Is it expected to

[Bug libstdc++/77641] std::variant copy-initialization fails for type with non-trivial constexpr ctor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77641 Jonathan Wakely changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libstdc++/77322] [C++11] std::function::swap should be noexcept.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77322 Jonathan Wakely changed: What|Removed |Added Target Milestone|--- |6.3 --- Comment #6 from Jonathan

[Bug libstdc++/72820] std::function can't store types with overloaded operator new

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72820 Jonathan Wakely changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libstdc++/77994] std::sample uses incorrect integer types internally

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77994 --- Comment #4 from Jonathan Wakely --- Author: redi Date: Mon Oct 17 17:03:09 2016 New Revision: 241263 URL: https://gcc.gnu.org/viewcvs?rev=241263=gcc=rev Log: Backport fixes to std::experimental::sample PR libstdc++/77994 *

[Bug libstdc++/77322] [C++11] std::function::swap should be noexcept.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77322 --- Comment #5 from Jonathan Wakely --- Author: redi Date: Mon Oct 17 17:03:31 2016 New Revision: 241266 URL: https://gcc.gnu.org/viewcvs?rev=241266=gcc=rev Log: Add noexcept to std::function swap Backport from mainline: 2016-08-22 Jonathan

[Bug libstdc++/72820] std::function can't store types with overloaded operator new

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72820 --- Comment #3 from Jonathan Wakely --- Author: redi Date: Mon Oct 17 17:03:19 2016 New Revision: 241264 URL: https://gcc.gnu.org/viewcvs?rev=241264=gcc=rev Log: Use ::new to avoid finding overloaded operator new Backport from mainline:

Re: [PATCH AArch64]Penalize vector cost for large loops with too many vect insns.

On Sat, Oct 15, 2016 at 01:07:12PM +1100, kugan wrote: > Hi Bin, > > On 15/10/16 00:15, Bin Cheng wrote: > >+/* Test for likely overcommitment of vector hardware resources. If a > >+ loop iteration is relatively large, and too large a percentage of > >+ instructions in the loop are

[Bug fortran/67091] [OOP] Bad result for type-bound procedures returning pointers to the intrinsic function ASSOCIATED

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67091 Paul Thomas changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

Re: [Patch] Backport fix for PR 52085 to gcc-5-branch?

Richard Biener writes: > On Mon, Oct 17, 2016 at 12:21 PM, Senthil Kumar Selvaraj > wrote: >> Hi, >> >> The fix for PR 52085 went into trunk when trunk was 6.0. I ran into the >> same issue on a gcc 5.x and found that the fix didn't get backported. >> >>

libgo patch committed: copy rdebug code from Go 1.7

This patch to libgo copies the rdebug code from the Go 1.7 runtime to libgo. While we're at it, this updates the runtime/debug package, and starts running its testsuite by default. I'm not sure why runtime/debug was not previously updated to 1.7. Doing that led me to fix some minor aspects of

[Bug libstdc++/72820] std::function can't store types with overloaded operator new

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72820 --- Comment #2 from Jonathan Wakely --- Author: redi Date: Mon Oct 17 16:50:43 2016 New Revision: 241250 URL: https://gcc.gnu.org/viewcvs?rev=241250=gcc=rev Log: Use ::new to avoid finding overloaded operator new Backport from mainline:

[Bug libstdc++/77322] [C++11] std::function::swap should be noexcept.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77322 --- Comment #4 from Jonathan Wakely --- Author: redi Date: Mon Oct 17 16:50:53 2016 New Revision: 241252 URL: https://gcc.gnu.org/viewcvs?rev=241252=gcc=rev Log: Add noexcept to std::function swap Backport from mainline: 2016-08-22 Jonathan

Re: [PATCH] Make -Wint-in-bool-context warn on suspicious shift ops

On 10/17/16 17:23, Markus Trippelsdorf wrote: > On 2016.09.29 at 18:52 +, Bernd Edlinger wrote: >> On 09/29/16 20:03, Jason Merrill wrote: >>> On Wed, Sep 28, 2016 at 12:09 PM, Bernd Edlinger >>> wrote: On 09/28/16 16:41, Jason Merrill wrote: > On Tue, Sep

[Bug libstdc++/77994] std::sample uses incorrect integer types internally

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77994 --- Comment #3 from Jonathan Wakely --- Author: redi Date: Mon Oct 17 16:50:37 2016 New Revision: 241249 URL: https://gcc.gnu.org/viewcvs?rev=241249=gcc=rev Log: Backport fixes to std::experimental::sample PR libstdc++/77994 *

Re: [PATCH] Reduce stack usage in sha512 (PR target/77308)

On 30/09/16 14:34, Bernd Edlinger wrote: On 09/30/16 12:14, Bernd Edlinger wrote: Eric Botcazou wrote: A comment before the SETs and a testcase would be nice. IIRC we do have stack size testcases via using -fstack-usage. Or -Wstack-usage, which might be more appropriate here. Yes. good

[Bug fortran/78013] New: unexpected 'has no IMPLICIT type' error for a type-bound function returning a procedure pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78013 Bug ID: 78013 Summary: unexpected 'has no IMPLICIT type' error for a type-bound function returning a procedure pointer Product: gcc Version: 7.0 Status: UNCONFIRMED

[PING #2] [PATCH] fix outstanding -Wformat-length failures (pr77735 et al.)

I'm still looking for a review of the patch below: https://gcc.gnu.org/ml/gcc-patches/2016-10/msg00043.html The patch should clean up the remaining test suite failures on ILP32 targets and also fixes up some remaining issues in the gimple-ssa-sprintf pass that stand in the way of

  1   2   3   >