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

On Tue, Nov 29, 2016 at 8: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 during the analysis and we should keep

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

On Thu, Dec 1, 2016 at 11:58 PM, Jeff Law wrote: > On 11/30/2016 11:59 AM, Jakub Jelinek wrote: >> >> 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

Avoid alloca(0) when temporarily propagating operands during threading

Martin's alloca work flagged this code as problematical. Essentially if we had a statement with no operands and the statement was not in the hash table, then we could end up performing alloca (0), which is inadvisable. We can safely just avoid the whole block of code if there are no

Re: [tree-tailcall] Check if function returns it's argument

On 2 December 2016 at 03:57, Jeff Law wrote: > On 12/01/2016 06:22 AM, Richard Biener wrote: >>> >>> Well after removing DECL_BY_REFERENCE, verify_gimple still fails but >>> differently: >>> >>> tail-padding1.C:13:1: error: RESULT_DECL should be read only when >>>

[PATCH] fix PR71721

Hi, it would be nice if uclinux targets are allowed to enable posix threads. Together with uClibc-ng/uClibc you can build m68k-nommu toolchain and enable old Linuxthreads instead of NPTL/TLS. With following change it is possible to build boost, which checks if gcc is build with threads enabled.

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77505 --- Comment #12 from Elizebeth Punnoose --- (In reply to kargl from comment #11) > Fixed on trunk. Closing. > > Elizebeth, Thanks for the patch. Thank you.

[Bug libgcc/68468] frv/bfin FDPIC toolchain build error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68468 Waldemar Brodkorb changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/78551] [5/6/7 Regression] Internal compiler error with constexpr initialization of union

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78551 --- Comment #7 from Vlad Petric --- Ok, so the example that I started this bug with is not standard compliant because it initialized different elements in a union with the constexpr constructor. The following does just one. I believe that the

[Bug libstdc++/78264] [7 regression] ICE in build_noexcept_spec, at cp/except.c:1196

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78264 --- Comment #6 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #5 from Eric Botcazou --- > Still present on Solaris. Jason, could you please have a look at this PR? Your patch (r241944) 2016-11-07 Jason Merrill

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

On 12/01/2016 02:15 AM, Jakub Jelinek wrote: On Thu, Dec 01, 2016 at 08:26:47AM +0100, Jakub Jelinek wrote: Isn't this too simplistic? I mean, if you have say dirtype of signed char and argmin say 4096 + 32 and argmax say 4096 + 64, (signed char) arg has range 32, 64, while I think your

[Bug fortran/78641] New: [OOP] ICE on polymorphic allocatable function in array constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78641 Bug ID: 78641 Summary: [OOP] ICE on polymorphic allocatable function in array constructor Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal

Re: [PATCH 1/9] print_rtx: implement support for reuse IDs (v2)

On Thu, 2016-12-01 at 16:05 -0700, Jeff Law wrote: > On 11/11/2016 02:15 PM, David Malcolm wrote: > > Posted earlier here: > > https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00651.html > > Link to earlier discussion: > > https://gcc.gnu.org/ml/gcc-patches/2016-10/msg01801.html > > > > This

[PATCH] PR fortran/78618 -- RANK() should not ICE

The attached patch fixes an ICE, a nearby whitespace issue, and removed the ATTRIBUTE_UNUSED tag. THe change has passed regression testing on x86_64-*-freebsd. Ok to commit? 2016-12-01 Steven G. Kargl PR fortran/78618 * check.c (gfc_check_rank): Remove

[PATCH 9/9] Add "__RTL" to cc1 (v6)

Changed in v6: - Handle EOF in c_parser_parse_rtl_body - Various fixups from review Changed in v5: - rebased from r242065 to r242392. In particular, this brings in the gimple FE; rewrote the "startwith" pass-skipping mechanism to work with both __GIMPLE and __RTL. - rewrote the "__RTL"

[PATCH 8a/9] Introduce class function_reader (v6)

Changed in v6: - split out dump-reading selftests into followup patches (target-independent, and target-specific) - removes unneeded headers from read-rtl-function.c - numerous other cleanups identified in review Changed in v5: - updated for change to emit_status::ensure_regno_capacity Changed

[PATCH 8d/9] Add x86_64-specific selftests for RTL function reader

This patch adds more selftests for class function_reader, where the dumps to be read contain x86_64-specific features. In an earlier version of the patch kit, these were handled using This version instead runs them via a target hook for running target-specific selftests, thus putting them within

[PATCH 8c/9] Add aarch64-specific selftests for RTL function reader

This patch adds more selftests for class function_reader, where the dumps to be read contain aarch64-specific features. In an earlier version of the patch kit, these were handled using #ifndef GCC_AARCH64_H to conditionalize running them. This version instead runs them via a target hook for

[PATCH 8b/9] Add target-independent selftests of RTL function reader

gcc/ChangeLog: * function-tests.c (selftest::verify_three_block_rtl_cfg): Remove "static". * read-rtl-function.c (selftest::assert_edge_at): New function. (ASSERT_EDGE): New macro. (selftest::test_loading_dump_fragment_1): New function.

Re: [PATCH 5/9] Introduce selftest::locate_file (v4)

On Thu, 2016-12-01 at 14:29 +0100, Bernd Schmidt wrote: > On 11/11/2016 10:15 PM, David Malcolm wrote: > > + /* Makefile.in has -fself-test=$(srcdir)/testsuite/selftests, so > > that > > + flag_self_test contains the path to the selftest subdirectory > > of the > > + source tree (without

[Bug target/78633] [7 Regression] [SH] libgcc/fp-bit.c:944:1: error: invalid rtl sharing found in the insn

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78633 --- Comment #2 from Kazumoto Kojima --- Looks not enough. Even with the patch, I got a similar ICE for lto case in testsuite: FAIL: gcc.dg/atomic/stdatomic-op-1.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (internal compiler error)

[PATCH] PR target/78639, Fix code generation on Power9

I discovered that my change in subversion id 242679, used a 'Y' constraint for movdi, when it should be using a 'wY'. 'Y' is for gpr load/stores, and it allows register+register address, while 'wY' is for the new register+offset instructions added in ISA 3.0, which does not include

Re: Pretty printers for versioned namespace

On 01/12/16 22:51 +0100, François Dumont wrote: On 29/11/2016 21:17, Jonathan Wakely wrote: On 28/11/16 22:19 +0100, François Dumont wrote: I am not fully happy with the replication in printers.py of StdRbtreeIteratorPrinter and StdExpAnyPrinter(SingleObjContainerPrinter in respectively

[Bug c++/78636] PPC Optimization Bug in Libelemental unit test

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

[Bug fortran/78640] New: [F2015] gfortran accepts invalid allocatable polymorphic result in pure function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78640 Bug ID: 78640 Summary: [F2015] gfortran accepts invalid allocatable polymorphic result in pure function Product: gcc Version: 7.0 Status: UNCONFIRMED Severity:

[Bug c++/68159] Demangler crash (GDB PR 19190)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68159 Natalie Silvanovich changed: What|Removed |Added CC||natashenka at google dot com ---

[Bug target/78639] Power9 bad code generation for cactusADM benchmark

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78639 --- Comment #2 from Michael Meissner --- Created attachment 40222 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40222=edit Bzip2 test case, compile with -g -O3 -mcpu=power9 -fgnu89-inline

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

On 12/01/2016 09:24 AM, Martin Sebor wrote: So, let's use another testcase, -O2 -W -Wall -fno-tree-vrp -fno-tree-ccp and again UB in it: volatile bool e; volatile int x; int main () { x = 123; *(char *) = x; bool f = e; x = __builtin_snprintf (0, 0, "%d", f); } This will store 1 into

[Bug target/78639] Power9 bad code generation for cactusADM benchmark

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78639 --- Comment #1 from Michael Meissner --- Created attachment 40221 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40221=edit Proposed patch to fix the problem

[Bug fortran/78618] ICE in gfc_check_rank, at fortran/check.c:3670

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

[Bug target/78639] Power9 bad code generation for cactusADM benchmark

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78639 Michael Meissner changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug target/78639] New: Power9 bad code generation for cactusADM benchmark

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78639 Bug ID: 78639 Summary: Power9 bad code generation for cactusADM benchmark Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug target/78614] [7 Regression] ICE error: invalid rtl sharing found in the insn (verify_rtx_sharing) gcc/emit-rtl.c:2743

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78614 --- Comment #23 from Bill Schmidt --- I've backported the insn_is_swappable_p bugfix to gcc-5-branch and gcc-6-branch. Thanks again for fixing that, Alan!

Re: [PATCH] Do not simplify "(and (reg) (const bit))" to if_then_else.

On 11/21/2016 05:36 AM, Dominik Vogt wrote: On Fri, Nov 11, 2016 at 12:10:28PM +0100, Dominik Vogt wrote: > On Mon, Nov 07, 2016 at 09:29:26PM +0100, Bernd Schmidt wrote: > > On 10/31/2016 08:56 PM, Dominik Vogt wrote: > > > > >combine_simplify_rtx() tries to replace rtx expressions with just

[Bug target/78633] [7 Regression] [SH] libgcc/fp-bit.c:944:1: error: invalid rtl sharing found in the insn

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78633 Kazumoto Kojima changed: What|Removed |Added CC||olegendo at gcc dot gnu.org ---

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

On Thu, Dec 01, 2016 at 11:48:03PM +0100, Bernd Schmidt wrote: > On 12/01/2016 11:43 PM, Jakub Jelinek wrote: > > > >so we'd need to slow shallow_copy_rtx down by adding switch (code) > >in there or something similar. > > Is there reason to assume it's time-critical? IMO eliminating the potential

[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 Status|NEW |RESOLVED

Re: [PATCH] PR fortran/77505 -- Treat negative character length as LEN=0

On Wed, Nov 30, 2016 at 05:13:28AM +, Punnoose, Elizebeth wrote: > Please excuse the messy formatting in my initial mail. Resending > with proper formatting. > > This patch checks for negative character length in the array > constructor, and treats it as LEN=0. > > A warning message is

[Bug tree-optimization/78586] [7 Regression] Wrong code caused by printf-return-value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78586 --- Comment #16 from Jakub Jelinek --- Author: jakub Date: Thu Dec 1 23:15:57 2016 New Revision: 243145 URL: https://gcc.gnu.org/viewcvs?rev=243145=gcc=rev Log: PR tree-optimization/78586 * gimple-ssa-sprintf.c

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

On Thu, Dec 01, 2016 at 03:55:58PM -0700, Jeff Law wrote: > On 11/30/2016 11:57 AM, Jakub Jelinek wrote: > >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

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77505 --- Comment #10 from kargl at gcc dot gnu.org --- Author: kargl Date: Thu Dec 1 23:11:35 2016 New Revision: 243143 URL: https://gcc.gnu.org/viewcvs?rev=243143=gcc=rev Log: 2016-12-01 Elizebeth Punnoose PR

[Bug rtl-optimization/78638] [7 regression] test cases gcc.target/powerpc/rlwimi-0.c and rlwimi-2.c fail starting with r243000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78638 Segher Boessenkool changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

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? 2016-11-30 Jakub Jelinek PR

[Bug target/78577] Fix define_insn operand types for vexturhlx, vexturhrx, vextuwlx, and vextuwrx patterns

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78577 kelvin at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

Re: [PATCH 1/9] print_rtx: implement support for reuse IDs (v2)

On 11/11/2016 02:15 PM, David Malcolm wrote: Posted earlier here: https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00651.html Link to earlier discussion: https://gcc.gnu.org/ml/gcc-patches/2016-10/msg01801.html This version: - eliminates the rtx_reuse_manager singleton - eliminates

Re: [PATCH] remove invalid "tail +16c"

On 11/22/2016 11:22 PM, ma.ji...@zte.com.cn wrote: Hi all, In "config/acx.m4", there are still some "tail +16c" which are invalid on POSIX systems. In my opinion， all "tail +16c" should be changed to "tail -c +16" directly, as most systems has accept the latter. And, to skip first 16

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

On 11/30/2016 11:59 AM, Jakub Jelinek wrote: 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

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

On 11/30/2016 11:57 AM, Jakub Jelinek wrote: 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

Re: [PATCH v2] improve folding of expressions that move a single bit around

On 12/01/2016 04:21 AM, Paolo Bonzini wrote: In code like the following from KVM: /* it is a read fault? */ error_code = (exit_qualification << 2) & PFERR_FETCH_MASK; it would be nicer to write /* it is a read fault? */ error_code = (exit_qualification &

[Bug target/71767] Endless stream of warnings when using GCC with -Wa,-q and Clang Integrated Assembler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 --- Comment #55 from Iain Sandoe --- (In reply to Jack Howarth from comment #54) > Shouldn't this be closed now as resolved? nope, it needs back-porting to 6.x and 5.x - will do that after it's been on trunk a while.

[Bug target/78577] Fix define_insn operand types for vexturhlx, vexturhrx, vextuwlx, and vextuwrx patterns

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78577 --- Comment #1 from kelvin at gcc dot gnu.org --- Author: kelvin Date: Thu Dec 1 22:52:07 2016 New Revision: 243141 URL: https://gcc.gnu.org/viewcvs?rev=243141=gcc=rev Log: gcc/ChangeLog: 2016-12-01 Kelvin Nilsen

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

On 12/01/2016 11:43 PM, Jakub Jelinek wrote: so we'd need to slow shallow_copy_rtx down by adding switch (code) in there or something similar. Is there reason to assume it's time-critical? IMO eliminating the potential for error by not having callers need to do this outweighs that concern.

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

On Thu, Dec 01, 2016 at 01:19:16PM +0100, Bernd Schmidt wrote: > On 11/30/2016 11:11 PM, Jakub Jelinek wrote: > >I run into the problem that while simplify_replace_rtx if it actually does > >copy_rtx (for y) or if it simplifies something through > >simplify_gen_{unary,binary,relational,ternary},

gcc-6-20161201 is now available

Snapshot gcc-6-20161201 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/6-20161201/ 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

Re: [PATCH] Fix runtime error: left shift of negative value (PR, ipa/78555).

On 12/01/2016 02:54 AM, Martin Liška wrote: As described in the PR, we do couple of shifts of a negative value. Fixed in the patch and couple of new unit tests are added. Patch can bootstrap on ppc64le-redhat-linux and survives regression tests. Ready to be installed? Martin

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

[Bug target/71767] Endless stream of warnings when using GCC with -Wa,-q and Clang Integrated Assembler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 --- Comment #54 from Jack Howarth --- Shouldn't this be closed now as resolved?

Re: [tree-tailcall] Check if function returns it's argument

On 12/01/2016 06:22 AM, Richard Biener wrote: Well after removing DECL_BY_REFERENCE, verify_gimple still fails but differently: tail-padding1.C:13:1: error: RESULT_DECL should be read only when DECL_BY_REFERENCE is set } ^ while verifying SSA_NAME nrvo_4 in statement # .MEM_3 = VDEF

[Bug rtl-optimization/78638] New: [7 regression] test cases gcc.target/powerpc/rlwimi-0.c and rlwimi-2.c fail starting with r243000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78638 Bug ID: 78638 Summary: [7 regression] test cases gcc.target/powerpc/rlwimi-0.c and rlwimi-2.c fail starting with r243000 Product: gcc Version: 7.0

[Bug c/78568] [5/6/7 Regression] Wtype-limits warning regression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78568 --- Comment #6 from Jakub Jelinek --- That is not how C++ c_fully_fold works. There it can be called multiple times, and it does some caching to avoid consuming too much time, but the caches can be flushed at certain times.

Re: [PATCH] PR 66149 & PR78235 dbxout_type_fields

On Thu, Dec 01, 2016 at 01:41:30PM -0500, David Edelsohn wrote: > TEMPLATE_DECL is defined in cp/cp-tree.def, which is included in > all-tree.def, which is included in tree-core.h, which is included in > tree.h, which is included in dbxout.c. That is clearly a bug, if TEMPLATE_DECL is used in the

[committed] dwarf2out.c: fix jit issue with early_dwarf_finished

All of the jit testcases that generate debuginfo appear to have been failing since r240228 on their 2nd in-process iteration on this assertion in set_early_dwarf's ctor: gcc_assert (! early_dwarf_finished); Root cause is that the global is never reset at the end of compilation, which this

[Bug fortran/37336] [F03] Finish derived-type finalization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37336 Bug 37336 depends on bug 59694, which changed state. Bug 59694 Summary: [F03] no finalization of an unused variable https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59694 What|Removed |Added

[Bug fortran/59694] [F03] no finalization of an unused variable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59694 Damian Rouson changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug other/78161] contrib/download_prerequisites fails on MacOS, Lubuntu, and Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78161 --- Comment #4 from Damian Rouson --- I'll close this because another developer is going to work on it so my last comment no longer applies.

Re: Pretty printers for versioned namespace

On 29/11/2016 21:17, Jonathan Wakely wrote: On 28/11/16 22:19 +0100, François Dumont wrote: Hi Here is a patch to fix pretty printers when versioned namespace is activated. You will see that I have hesitated in making the fix independant of the version being used. In source files you

Re: [PATCH 8/9] Introduce class function_reader (v4)

On Thu, 2016-12-01 at 15:40 +0100, Bernd Schmidt wrote: Thanks for looking at this. > On 11/11/2016 10:15 PM, David Malcolm wrote: > > #include "gt-aarch64.h" > > diff --git a/gcc/config/i386/i386.c b/gcc/config/i386/i386.c > > index 6c608e0..0dda786 100644 > > --- a/gcc/config/i386/i386.c > >

[SPARC] Preparatory work for switch to LRA

The switch will very likely not happen for GCC 7, but an experimental support can probably be introduced. The attached patch adds the famous -mlra option and rescues straightforward changes by DaveM. Tested on SPARC/Solaris, applied on the mainline. 2016-12-01 Eric Botcazou

[Bug fortran/78279] ICE in identical_array_ref, at fortran/dependency.c:104

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

[Bug fortran/78279] ICE in identical_array_ref, at fortran/dependency.c:104

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78279 --- Comment #5 from kargl at gcc dot gnu.org --- Author: kargl Date: Thu Dec 1 21:28:41 2016 New Revision: 243134 URL: https://gcc.gnu.org/viewcvs?rev=243134=gcc=rev Log: 2016-12-01 Steven G. Kargl PR

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

On 12/01/2016 05:49 PM, Martin Sebor wrote: Okay, thanks for the clarification. One other question though. Why would the probability be near zero? In the absence of any hints the expression 2 != sprintf(d, "%i", 12) should have a very high probability of being true, near 100% in fact. I ask

[Bug fortran/78279] ICE in identical_array_ref, at fortran/dependency.c:104

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78279 --- Comment #4 from kargl at gcc dot gnu.org --- Author: kargl Date: Thu Dec 1 21:05:49 2016 New Revision: 243133 URL: https://gcc.gnu.org/viewcvs?rev=243133=gcc=rev Log: 016-12-01 Steven G. Kargl PR fortran/78279

Re: [Patch 1/2 PR78561] Rename get_pool_size to get_pool_size_upper_bound

On 12/01/2016 08:29 AM, James Greenhalgh wrote: Hi, There's no functional change in this patch, just a rename. The size recorded in "offset" is only ever incremented as we add new items to the constant pool. But this information can become stale where those constant pool entries would not get

[Committed] PR fortran/78279 -- convert gcc_assert to internal error

I've committed the attached patch, which converts a gcc_assert() to a conditional express tha may call gfc_internal_error().o 2016-12-01 Steven G. Kargl PR fortran/78279 * dependency.c (identical_array_ref): Convert gcc_assert to conditional and

[Bug fortran/78279] ICE in identical_array_ref, at fortran/dependency.c:104

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78279 --- Comment #3 from kargl at gcc dot gnu.org --- Author: kargl Date: Thu Dec 1 20:37:55 2016 New Revision: 243131 URL: https://gcc.gnu.org/viewcvs?rev=243131=gcc=rev Log: 2016-12-01 Steven G. Kargl PR

[Bug target/78631] [Intel MPX] libmpxwrappers shared library leads to a non-bounds-preserving memcpy()

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78631 Ilya Enkovich changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

Go patch committed: add slice initializers to the GC root list

As of https://golang.org/cl/32917 we can put slice initializers in the .data section. The program can still change the values in those slices. That means that if the slice elements can contain pointers, we need to register the entire initializer as a GC root. This would be straightforward

[Bug c++/56480] Explicit specialization in a namespace enclosing the specialized template

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56480 Jason Merrill changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/78101] PowerPC 64-bit little endian fusion failure with -O3 -mcpu=power9

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78101 Michael Meissner changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/78101] PowerPC 64-bit little endian fusion failure with -O3 -mcpu=power9

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78101 --- Comment #3 from Michael Meissner --- Author: meissner Date: Thu Dec 1 19:26:15 2016 New Revision: 243128 URL: https://gcc.gnu.org/viewcvs?rev=243128=gcc=rev Log: [gcc] 2016-12-01 Michael Meissner

[Bug c++/78637] [7 Regression] ICE on invalid C++ code on x86_64-linux-gnu (internal compiler error: in pop_namespace, at cp/name-lookup.c:3826)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78637 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |NEW Known to work|

[Bug c++/78635] [6/7 Regression] internal compiler error: in output_constructor_regular_field, at varasm.c:4989

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78635 Martin Liška changed: What|Removed |Added CC||marxin at gcc dot gnu.org,

Re: GCC libatomic ABI specification draft

Hi Szabolcs, > On Nov 29, 2016, at 3:11 AM, Szabolcs Nagy wrote: > > On 17/11/16 20:12, Bin Fan wrote: >> >> Although this ABI specification specifies that 16-byte properly aligned >> atomics are inlineable on platforms >> supporting cmpxchg16b, we document the caveats

[Bug debug/66149] ICE: tree check: expected field_decl, have template_decl in int_bit_position, at tree.h:5012 with -std=c++14 -gstabs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66149 David Edelsohn changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/78235] [7 Regression] libstdc++ testsuite run.cc ICE in int_bit_position

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78235 David Edelsohn changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/78235] [7 Regression] libstdc++ testsuite run.cc ICE in int_bit_position

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78235 --- Comment #6 from David Edelsohn --- Author: dje Date: Thu Dec 1 18:58:47 2016 New Revision: 243126 URL: https://gcc.gnu.org/viewcvs?rev=243126=gcc=rev Log: PR debug/66419 PR c++/78235 * dbxout.c (dbxout_type_fields): Skip TEMPLATE_DECLs.

[Bug tree-optimization/66419] [6 regression] FAIL: gcc.target/aarch64/aapcs64/va_arg-6.c execution, -O3 -g

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66419 --- Comment #6 from David Edelsohn --- Author: dje Date: Thu Dec 1 18:58:47 2016 New Revision: 243126 URL: https://gcc.gnu.org/viewcvs?rev=243126=gcc=rev Log: PR debug/66419 PR c++/78235 * dbxout.c (dbxout_type_fields): Skip TEMPLATE_DECLs.

[Bug target/78255] [5/6/7 regression] Indirect sibling call causing wrong code generation for ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78255 --- Comment #9 from Jeffrey A. Law --- Also note that on some targets indirect calls have a different ABI than calls to named function. SO changing between direct and indirect calls is strictly forbidden on some targets. I suspect there's some

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

Dump sent privately. Yes, I meant "x". AIX defaults to 32 bit. - David On Thu, Dec 1, 2016 at 1:31 PM, Andre Vehreschild wrote: > Hi all, > > I am sorry, but the initial mail as well as Dominique answer puzzles me: > > David: I do expect to > > write (*,*) any > > not

[Bug c/78568] [5/6/7 Regression] Wtype-limits warning regression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78568 --- Comment #5 from joseph at codesourcery dot com --- c_fully_fold should not be asked to fold the same expression more than once. When a subexpression is folded during parsing, for whatever reason, the result should be wrapped in a tree

Re: [PATCH] PR 66149 & PR78235 dbxout_type_fields

On 12/01/2016 11:41 AM, David Edelsohn wrote: On Thu, Dec 1, 2016 at 1:25 PM, Jeff Law wrote: On 12/01/2016 09:15 AM, David Edelsohn wrote: A number of the "variant" testcases fail to build on AIX and targets that use stabs. The failure looks like:

Re: [PATCH] PR 66149 & PR78235 dbxout_type_fields

On Thu, Dec 1, 2016 at 1:25 PM, Jeff Law wrote: > On 12/01/2016 09:15 AM, David Edelsohn wrote: >> >> A number of the "variant" testcases fail to build on AIX and targets >> that use stabs. The failure looks like: >> >>

Re: [PATCH] avoid calling alloca(0)

On 11/30/2016 09:09 PM, Martin Sebor wrote: 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

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

Hi all, I am sorry, but the initial mail as well as Dominique answer puzzles me: David: I do expect to write (*,*) any not being compilable at all, because "any" is an intrinsic function and I suppose that gfortran is not able to print it. At best it gives an address. So am I right

[Bug c++/78637] New: ICE on invalid C++ code on x86_64-linux-gnu (internal compiler error: in pop_namespace, at cp/name-lookup.c:3826)

COLLECT_LTO_WRAPPER=/usr/local/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/7.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../gcc-source-trunk/configure --enable-languages=c,c++,lto --prefix=/usr/local/gcc-trunk --disable-bootstrap Thread model: posix gcc version 7.0.0 20161201 (experimental

[Bug middle-end/78629] vec.h: null pointer passed as argument 1, which is declared to never be null

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78629 --- Comment #3 from prathamesh3492 at gcc dot gnu.org --- Fixed by r243125, forgot to add PR number to changelog in the patch :/

Re: [PATCH] PR 66149 & PR78235 dbxout_type_fields

On 12/01/2016 09:15 AM, David Edelsohn wrote: A number of the "variant" testcases fail to build on AIX and targets that use stabs. The failure looks like: /tmp/GCC/powerpc-ibm-aix7.2.0.0/libstdc++-v3/include/variant:956: internal compiler error: tree check: expected field_decl, have

[Bug c++/78636] PPC Optimization Bug in Libelemental unit test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78636 --- Comment #2 from rhl --- Created attachment 40220 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40220=edit and the output of valgrind after remove offending Output function in favor out std::cout

[Bug c++/78636] PPC Optimization Bug in Libelemental unit test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78636 --- Comment #1 from rhl --- Created attachment 40219 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40219=edit this is the valgrind output when the segfault occurs

[Bug c++/78636] New: PPC Optimization Bug in Libelemental unit test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78636 Bug ID: 78636 Summary: PPC Optimization Bug in Libelemental unit test Product: gcc Version: 6.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Re: [PATCH] have __builtin_object_size handle POINTER_PLUS with non-const offset (pr 77608)

Sure - but then you maybe instead want to check for op being in range [0, max-of-signed-type-of-op] instead? So similar to expr_not_equal_to add a expr_in_range helper? Your function returns true for sizetype vars even if it might be effectively signed, like for sizetype i_1 = -4; i_2 = i_1

  1   2   3   4   >