[PATCH] Fix sporadic failure of gcc.dg/cpp/pr66415-1.c

Hi, it turns out that in this test case the expected output depends on the COLUMNS setting of the terminal where the test suite is started. With less than 82 columns the multiline output is not as expected. The reason for that seems to be at diagnostic_set_caret_max_width where it is dependent

[Bug c++/27336] "this" pointer is not assumed to be not null

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27336 --- Comment #8 from Guillaume Melquiond --- It is partly fixed. In callee position, GCC now knows that "this" is non-null. But in caller position, GCC still cannot make use of that information to remove non-null checks from dynamic casts. The

[Bug c/52952] Wformat location info is bad (wrong column number)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52952 --- Comment #48 from Bernd Edlinger --- somethin like that fixes it for me: Index: pr66415-1.c === --- pr66415-1.c (revision 239624) +++ pr66415-1.c (working copy) @@ -1,6 +1,7 @@

[Bug c/52952] Wformat location info is bad (wrong column number)

ted passes3 /home/ed/gnu/gcc-build/gcc/xgcc version 7.0.0 20160819 (experimental) (GCC) COLUMNS=80 make check-gcc-c RUNTESTFLAGS="cpp.exp=pr66415-1.c" ... Running /home/ed/gnu/gcc-trunk/gcc/testsuite/gcc.dg/cpp/cpp.exp ... FAIL: gcc.dg/cpp/pr66415-1.c expected multiline pattern lines

[Bug debug/49348] DW_TAG_template_* DIEs missing from template specializations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49348 Alexandre Oliva changed: What|Removed |Added CC||aoliva at gcc dot gnu.org --- Comment

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

> > > Patch #5 and beyond: Further optimization work. > > > > As one of the next steps I'd like to make this feature available > > to user-defined sprintf-like functions decorated with attribute > > format. To do that, I'm thinking of adding either a fourth > > (optional) argument to attribute

Re: protected alloca class for malloc fallback

On Aug 10, 2016, at 10:03 AM, Oleg Endo wrote: > > Or just wait until people have agreed to switch to C++11 or C++14. I > don't think in practice anybody uses an C++11-incapable GCC to build a > newer GCC these days. I use the system gcc 4.4.7 on RHEL to build a newer

Re: [Patch, testsuite] Skip tests that expect 4 byte alignment for avr

On Aug 11, 2016, at 12:40 AM, Senthil Kumar Selvaraj wrote: > > The below patch adds the AVR target to the list of targets that don't > have natural_alignment_32. It also skips ipa/propalign-*.c > tests (which expect 4 byte alignment), if both >

Re: [PATCH] newlib-stdint.h: Remove 32 bit longs

RTEMS uses the PRI constants and we don't see warnings. Is there a specific test case which would demonstrate this is actually broken. The file newlib-stdint.h will impact more targets than Zephyr and I think they owe a demo case. On August 19, 2016 7:37:22 PM EDT, Andrew Pinski

[Bug tree-optimization/61839] More optimize opportunity for VRP

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61839 --- Comment #3 from kugan at gcc dot gnu.org --- Author: kugan Date: Sat Aug 20 01:18:09 2016 New Revision: 239637 URL: https://gcc.gnu.org/viewcvs?rev=239637=gcc=rev Log: gcc/testsuite/ChangeLog: 2016-08-20 Kugan Vivekanandarajah

[Bug c++/77306] Unable to specify visibility for explicit template instantiations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77306 --- Comment #1 from James Abbatiello --- Created attachment 39478 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39478=edit Patch

[Bug c++/77306] New: Unable to specify visibility for explicit template instantiations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77306 Bug ID: 77306 Summary: Unable to specify visibility for explicit template instantiations Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal

[Bug lto/77305] [7 Regression] -fdump-tree-all and -flto causes ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77305 --- Comment #1 from Andrew Pinski --- https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01456.html

Re: [PATCH] Make clone materialization an IPA pass

On Thu, Aug 18, 2016 at 1:14 AM, Richard Biener wrote: > > The following patch makes it possible to add statistic counters to > update-ssa. Clone materialization ends up updating SSA form from > a context with current_pass being NULL - wrapping materialize_all_clones > into a

[Bug lto/77305] [7 Regression] -fdump-tree-all and -flto causes ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77305 Andrew Pinski changed: What|Removed |Added Keywords||ice-on-valid-code Target

[Bug lto/77305] New: [7 Regression] -fdump-tree-all and -flto causes ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77305 Bug ID: 77305 Summary: [7 Regression] -fdump-tree-all and -flto causes ICE Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal Priority: P3

Re: [PATCH] Restrict jump threading statement simplifier to scalar types (PR71077)

On Fri, 19 Aug 2016, David Malcolm wrote: > On Fri, 2016-08-19 at 19:25 -0400, Patrick Palka wrote: > > On Fri, 19 Aug 2016, Yuri Rumyantsev wrote: > > > > > Hi, > > > > > > Here is a simple test-case to reproduce 176.gcc failure (I run it > > &

Re: [PATCH] Restrict jump threading statement simplifier to scalar types (PR71077)

On Fri, 2016-08-19 at 19:25 -0400, Patrick Palka wrote: > On Fri, 19 Aug 2016, Yuri Rumyantsev wrote: > > > Hi, > > > > Here is a simple test-case to reproduce 176.gcc failure (I run it > > on > > Haswell machine). > > Using 20160819 compiler build

[PATCH] selftest.h: add ASSERT_STR_CONTAINS

More enabling work for some new selftests I'm working on. Successfully bootstrapped on x86_64-pc-linux-gnu. OK for trunk? gcc/ChangeLog: * selftest.c (selftest::assert_str_contains): New function. (selftest::test_assertions): Verify ASSERT_STR_CONTAINS. * selftest.h

[PATCH], Patch #6, Improve vector short/char splat initialization on PowerPC

This patch is a follow up to patch #5. It adds the support to use the Altivec VSPLTB/VSPLTH instructions if you are creating a vector char or vector short where each element is the same (but not constant) on 64-bit systems with direct move. The patch has been part of the larger set of patches

Re: [PATCH] Handle VECTOR_CST in integer_nonzerop()

On Fri, Aug 19, 2016 at 7:30 PM, Patrick Palka wrote: > integer_nonzerop() currently unconditionally returns false for a > VECTOR_CST argument. This is confusing because one would expect that > integer_onep(x) => integer_nonzerop(x) for all x but that is currently > not the

Re: [PATCH] newlib-stdint.h: Remove 32 bit longs

On Fri, Aug 19, 2016 at 12:16 PM, Andy Ross wrote: > We ran into this issue in the Zephyr project with our toolchain (gcc > built with --enable-newlib). Basically GCC appears to be honoring a > legacy requirement to give newlib a "long" instead of "int" for >

[PATCH] Handle VECTOR_CST in integer_nonzerop()

integer_nonzerop() currently unconditionally returns false for a VECTOR_CST argument. This is confusing because one would expect that integer_onep(x) => integer_nonzerop(x) for all x but that is currently not the case. For a VECTOR_CST of all ones i.e. {1,1,1,1}, integer_onep() returns true but

[PATCH] Improve readability of debug_tree() dumps for SSA_NAME and VECTOR_CST

* For SSA_NAME: Print the ssa name's def stmt on its own line. Before: unit size align 32 symtab 0 alias set -1 canonical type 0x7688a888 precision 32 min max context pointer_to_this > unsigned V8SI size unit size

Re: [PATCH] Restrict jump threading statement simplifier to scalar types (PR71077)

On Fri, 19 Aug 2016, Yuri Rumyantsev wrote: > Hi, > > Here is a simple test-case to reproduce 176.gcc failure (I run it on > Haswell machine). > Using 20160819 compiler build we get: > gcc -O3 -m32 -mavx2 test.c -o test.ref.exe > /users/ysrumyan/isse_6866$ ./test.ref.exe &

[Bug c++/77304] New: ICE on C++ code with invalid template parameter: in gimplify_expr, at gimplify.c:11260

Thread model: posix gcc version 7.0.0 20160819 (experimental) [trunk revision 239608] (GCC) $ $ g++-trunk -c small.cpp small.cpp:5:14: error: ‘struct S’ is not a valid type for a template non-type parameter template < S > void f () {} ^ small.cpp: In static member function ‘

Re: [Patch] Disable text mode translation in ada for Cygwin

On 8/19/2016 20:49, Arnaud Charlet wrote: >>> Text mode translation should not be done for Cygwin, especially since it >>> does not >>> support unicode setmode calls. This also fixes ada builds for Cygwin. >>> >>> OK for trunk? >> >> Ping? > > Can you send the link to your original submission for

[Bug tree-optimization/71831] __builtin_object_size poor results with no optimization

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

[PATCH] tree-optimization/71831 - __builtin_object_size poor results with no optimization

As requested in the review of the following patch https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01363.html attached is the small enhancement to compute_builtin_object_size to make the function usable even without optimization without the full overhead of the tree-object-size pass. The

[Bug libstdc++/77303] New: std::max_element not constexpr with -D_GLIBCXX_DEBUG

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77303 Bug ID: 77303 Summary: std::max_element not constexpr with -D_GLIBCXX_DEBUG Product: gcc Version: 6.1.1 Status: UNCONFIRMED Severity: normal Priority: P3

[PATCH], Patch #5, Improve vector int initialization on PowerPC

This is a rewrite of patch #3 to improve vector int initialization on the PowerPC 64-bit systems wtih direct move (power8, and forthcoming power9). This patch adds full support for doing vector int initialization in the GPR and vector registers, rather than creating a stack temporary, doing 4

[committed] Reimplement removal fix-it hints in terms of replace

This patch eliminates class fixit_remove, reimplementing rich_location::add_fixit_remove in terms of replacement with the empty string. Deleting the removal subclass simplifies fixit-handling code, as we only have two concrete fixit_hint subclasses to deal with, rather than three. The patch also

[Bug c/52952] Wformat location info is bad (wrong column number)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52952 Bernd Edlinger changed: What|Removed |Added CC||bernd.edlinger at hotmail dot de ---

Add minimal _FloatN, _FloatNx built-in functions [version 2]

[Version 2 of this patch updates the testcases to use dg-add-options as in the final version of the _FloatN patch that went in; there are no changes of substance outside the testsuite. Version 1 was .] This patch adds a minimal set of

[Bug tree-optimization/62171] restrict pointer to struct with restrict pointers parm doesn't prevent aliases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62171 --- Comment #18 from vries at gcc dot gnu.org --- dg-options line was removed on trunk at https://gcc.gnu.org/viewcvs?rev=237745=gcc=rev

[Bug tree-optimization/62171] restrict pointer to struct with restrict pointers parm doesn't prevent aliases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62171 --- Comment #17 from ncahill_alt at yahoo dot com --- This was the only test that failed for me, the others were debug info in LTO mode. I'm very glad that GCC 6.1.0 works so well and built cleanly like it did. This test was a minor thing

Replacement for the .stabs directive

Hello Everyone , We have the legacy code ,that uses the .stabs directive quiet often in the source code like .stabs "symbol_name", 100, 0, 0, 0 + .label_one f; .label_one stmt and ,the above code is wrapped with the inline asm in the c source file . we are using clang 3.8(with

[Bug c++/27336] "this" pointer is not assumed to be not null

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27336 Manuel López-Ibáñez changed: What|Removed |Added CC||manu at gcc dot gnu.org ---

[Bug c++/77298] -Wnonnull-compare only emitted for code which is invoked

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77298 --- Comment #8 from Manuel López-Ibáñez --- (In reply to Martin Sebor from comment #6) > Yes, that makes sense to me as an explanation of the limitation of the GCC > implementation and a solution/workaround for it. I don't think it's >

[Bug tree-optimization/71550] [7 Regression] wrong code at -O3 on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71550 --- Comment #4 from Jeffrey A. Law --- This has gone latent on the trunk, but I'm pretty sure the core issues remain. Looking deeper into the problem, this may be another case of jump threading invalidating the cached loop iteration

[PATCH] newlib-stdint.h: Remove 32 bit longs

We ran into this issue in the Zephyr project with our toolchain (gcc built with --enable-newlib). Basically GCC appears to be honoring a legacy requirement to give newlib a "long" instead of "int" for __INT32_TYPE__, which then leaks out through the current newlib headers as a long-valued

[Bug c++/77302] New: partial specialization marked as ambiguous

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77302 Bug ID: 77302 Summary: partial specialization marked as ambiguous Product: gcc Version: 6.1.1 Status: UNCONFIRMED Severity: minor Priority: P3 Component: c++

[Bug debug/59319] gcc does not emit DW_AT_friend or DW_TAG_friend

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59319 Alexandre Oliva changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[PR59319] output friends in debug info

This is not a finished patch. There are two issues I'd like feedback on before a final submission. See them below. First, a general description. Handling non-template friends is kind of easy, but it required a bit of infrastructure in dwarf2out to avoid (i) forcing debug info for unused types

[PATCH, i386]: Fix PR77270, Flag -mprftchw is shared with 3dnow for -march=k8

Hello! There is a problem with -march=native, when -m3dnow and -mno-prfchw are added to the compilation flags. The prefetchw is enabled by -m3dnow, but TARGET_PRFCHW is never enabled, since explicit -mno-prfchw is passed by the driver. Attached patch fixes this by divorcing TARGET_3DNOW from

[Bug target/77270] Flag -mprftchw is shared with 3dnow for -march=k8

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77270 --- Comment #4 from uros at gcc dot gnu.org --- Author: uros Date: Fri Aug 19 18:14:03 2016 New Revision: 239626 URL: https://gcc.gnu.org/viewcvs?rev=239626=gcc=rev Log: PR target/77270 * config/i386/i386.c

[Bug middle-end/77301] __builtin_object_size incorrect for an array in a struct referenced by a pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77301 --- Comment #2 from Martin Sebor --- Thanks. As surprising as that seems, it would explain the output of the test case in comment #0, even though it's not at all obvious from the manual. But if change the test case like below I get three

[Bug tree-optimization/62171] restrict pointer to struct with restrict pointers parm doesn't prevent aliases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62171 --- Comment #16 from ncahill_alt at yahoo dot com --- (In reply to Richard Biener from comment #15) > (In reply to ncahill_alt from comment #14) > > This test is failing for me in GCC 6.1.0 (i386). It complains about having > > no vectype. > >

[Bug target/32187] Complex __float128 is rejected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32187 --- Comment #12 from joseph at codesourcery dot com --- You can now use _Complex _Float128. Given that, it's not obvious that _Complex __float128, with the legacy __float128 type name, should be supported (although not supporting that means

[Bug c++/77298] -Wnonnull-compare only emitted for code which is invoked

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77298 --- Comment #7 from Jakub Jelinek --- Different warnings are simply done at different compilation phases. This is similar to how you get only a subset of FE warnings on uninstantiated templates, only something can be warned reliably at that

[Bug target/32187] Complex __float128 is rejected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32187 --- Comment #11 from Joseph S. Myers --- Author: jsm28 Date: Fri Aug 19 17:43:26 2016 New Revision: 239625 URL: https://gcc.gnu.org/viewcvs?rev=239625=gcc=rev Log: Implement C _FloatN, _FloatNx types. ISO/IEC TS 18661-3:2015 defines C bindings

[Bug middle-end/77301] __builtin_object_size incorrect for an array in a struct referenced by a pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77301 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug rtl-optimization/77289] [7 Regression] ICE in extract_constrain_insn, at recog.c:2212 on powerpc64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77289 Peter Bergner changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c++/77298] -Wnonnull-compare only emitted for code which is invoked

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77298 --- Comment #6 from Martin Sebor --- Yes, that makes sense to me as an explanation of the limitation of the GCC implementation and a solution/workaround for it. I don't think it's something users unfamiliar with GCC internals think of, though.

[Bug middle-end/77301] New: __builtin_object_size incorrect for an array in a struct referenced by a pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77301 Bug ID: 77301 Summary: __builtin_object_size incorrect for an array in a struct referenced by a pointer Product: gcc Version: 7.0 Status: UNCONFIRMED Severity:

Re: Implement C _FloatN, _FloatNx types [version 6]

On Fri, 2016-08-19 at 16:51 +, Joseph Myers wrote: > On Fri, 19 Aug 2016, David Malcolm wrote: > > > Please could you take this opportunity to add some examples to the > > header comment for that function, both for the common cases e.g. > > "f", > > and for the new suffixes; nothing in the

[Bug c++/77298] -Wnonnull-compare only emitted for code which is invoked

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77298 --- Comment #5 from Jakub Jelinek --- You can always use -fkeep-inline-functions to get the warning even for unused inlines (by forcing them to be emitted). -Wnonnull-compare isn't the only warning that isn't performed in the FEs early, think

Re: Implement C _FloatN, _FloatNx types [version 6]

On Fri, 19 Aug 2016, David Malcolm wrote: > Please could you take this opportunity to add some examples to the > header comment for that function, both for the common cases e.g. "f", > and for the new suffixes; nothing in the patch body appears to document > them. (ideally, referencing the

[Bug c++/77298] -Wnonnull-compare only emitted for code which is invoked

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

[Bug tree-optimization/73714] [Regression 7] Incorrect unsigned long long arithmetic optimization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=73714 Marc Glisse changed: What|Removed |Added CC||marc.glisse at normalesup dot org ---

Re: [PATCH] Simplify dg-options for tests using pthreads

On 18/08/16 09:06 +0100, Jonathan Wakely wrote: It's been several years now that Solaris supported -pthread as well as -pthreads, so there's no need to have separate dg-options directives for Solaris. This patch removes all the lines: // { dg-options "... -pthreads" { target *-*-solaris* } }

[Bug c/77292] Spurious warning: logical not is only applied to the left hand side of comparison

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77292 --- Comment #13 from Segher Boessenkool --- (In reply to Manuel López-Ibáñez from comment #12) > (In reply to Segher Boessenkool from comment #11) > > Both of these suggestions are not so good. "!(a == b)" is better written > > as "a != b", and

[Bug target/77300] New: [MIPS] incorrectly moves instruction containing local GOT16 relocation into a delay slot

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77300 Bug ID: 77300 Summary: [MIPS] incorrectly moves instruction containing local GOT16 relocation into a delay slot Product: gcc Version: unknown Status: UNCONFIRMED

[Bug target/77270] Flag -mprftchw is shared with 3dnow for -march=k8

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77270 Uroš Bizjak changed: What|Removed |Added Keywords|wrong-code | Status|UNCONFIRMED

Re: Implement C _FloatN, _FloatNx types [version 6]

On Fri, 19 Aug 2016, Szabolcs Nagy wrote: > On 17/08/16 21:17, Joseph Myers wrote: > > Although there is HFmode support for ARM and AArch64, use of that for > > _Float16 is not enabled. Supporting _Float16 would require additional > > work on the excess precision aspects of TS 18661-3: there are

[Bug rtl-optimization/64082] virtual register elimination doing bad for local array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64082 Joey Ye changed: What|Removed |Added CC||joey.ye at arm dot com --- Comment #1 from

[Bug c++/77298] -Wnonnull-compare only emitted for code which is invoked

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77298 --- Comment #3 from Martin Sebor --- I should add that Clang issues the warning for all three functions: $ /build/llvm-trunk/bin/clang -S -Wall -Wextra -Wpedantic z.C z.C:2:21: warning: 'this' pointer cannot be null in well-defined C++ code;

[Bug c++/77297] parenthesis suppress/silences all warnings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77297 --- Comment #2 from Manuel López-Ibáñez --- *** Bug 77299 has been marked as a duplicate of this bug. ***

Re: [PATCH] Define std::not_fn for C++17

On 19/08/16 16:46 +0100, Jonathan Wakely wrote: This updates std::experimental::not_fn to match the C++17 semantics (which are a superset of the Library Fundamentals v2 semantics) and then copies it to std::not_fn as well. * doc/xml/manual/status_cxx2017.xml: Update status of not_fn.

[Bug c++/77298] -Wnonnull-compare only emitted for code which is invoked

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77298 Manuel López-Ibáñez changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug c++/77299] No warning for unused "INT64_MAX" and similar constants

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77299 Manuel López-Ibáñez changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug c++/77298] -Wnonnull-compare only emitted for code which is invoked

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77298 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment #2

Re: Implement C _FloatN, _FloatNx types [version 6]

On Fri, 2016-08-19 at 14:40 +, Joseph Myers wrote: > On Fri, 19 Aug 2016, Richard Biener wrote: > > > > > Can you quickly verify if LTO works with the new types? I > > > > don't see anything > > > > that would prevent it but having new global trees and backends > > > > initializing them > >

[PATCH] Define std::not_fn for C++17

This updates std::experimental::not_fn to match the C++17 semantics (which are a superset of the Library Fundamentals v2 semantics) and then copies it to std::not_fn as well. * doc/xml/manual/status_cxx2017.xml: Update status of not_fn. * doc/html/*: Regenerate. *

[committed] Fix handling of ASSOCIATE in OpenMP resolving (PR fortran/71014)

Hi! The saving+clearing and restoring of OpenMP state during gfc_resolve is meant for when during resolving of one subroutine/function etc. we resolve another one, but apparently ASSOCIATE blocks (and BLOCK, though that isn't supported yet - OpenMP 4.5 only supports Fortran 2003, not 2008) add

[PATCH] Define std::atomic::is_always_lock_free for C++17

Another new C++17 feature. * include/std/atomic (atomic::is_always_lock_free): Define. * testsuite/29_atomics/atomic/60695.cc: Adjust dg-error lineno. * testsuite/29_atomics/atomic/is_always_lock_free.cc: New. *

[Bug c++/77297] parenthesis suppress/silences all warnings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77297 Manuel López-Ibáñez changed: What|Removed |Added Keywords||diagnostic

[PATCH] Fix ambiguities in C++17 mode

This fixes some more test FAILs when using -std=gnu++17, due to names in std::experimental now also being in std. * include/experimental/tuple (apply): Qualify call to __apply_impl. * include/std/tuple (apply): Likewise. * testsuite/experimental/system_error/value.cc: Fix

[committed] Add testcase (PR fortran/72744)

Hi! This got also fixed by PR69281 fix I've just committed, I've added the testcase too. 2016-08-19 Jakub Jelinek PR fortran/72744 * gfortran.dg/gomp/pr72744.f90: New test. --- gcc/testsuite/gfortran.dg/gomp/pr72744.f90.jj 2016-08-19

[committed] Fix OpenMP ICE (PR fortran/69281)

Hi! On the following testcase we ICE because the BLOCK that is initially in the BIND_EXPR on the OMP_PARALLEL/TASK/TARGET body contains a VAR_DECL for -fstack-arrays added artificial VLA. Later on for move_sese_* reasons this is the BLOCK used for the moving, which means that a copy of the

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

On 08/19/2016 09:29 AM, Martin Sebor wrote: My biggest concern with this iteration is the tight integration between the optimization and warning. We generally avoid that kind of tight integration such that enabling the warning does not affect the optimization and vice-versa. So ISTM you have

[Bug fortran/71014] associate statement inside omp parallel do appears to disable default private attribute for inner loop indices

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71014 --- Comment #10 from Jakub Jelinek --- Author: jakub Date: Fri Aug 19 15:30:33 2016 New Revision: 239620 URL: https://gcc.gnu.org/viewcvs?rev=239620=gcc=rev Log: PR fortran/71014 * resolve.c (gfc_resolve): For

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

My biggest concern with this iteration is the tight integration between the optimization and warning. We generally avoid that kind of tight integration such that enabling the warning does not affect the optimization and vice-versa. So ISTM you have to do the analysis if the optimization or

[Bug fortran/72744] ICE in verify_ssa, at tree-ssa.c:1039

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72744 --- Comment #3 from Jakub Jelinek --- Author: jakub Date: Fri Aug 19 15:28:59 2016 New Revision: 239619 URL: https://gcc.gnu.org/viewcvs?rev=239619=gcc=rev Log: PR fortran/72744 * gfortran.dg/gomp/pr72744.f90: New test. Added:

[Bug fortran/69281] gfortran ICE on temporary array in function call with -fstack-arrays -fopenmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69281 --- Comment #3 from Jakub Jelinek --- Author: jakub Date: Fri Aug 19 15:27:40 2016 New Revision: 239618 URL: https://gcc.gnu.org/viewcvs?rev=239618=gcc=rev Log: PR fortran/69281 * trans-openmp.c (gfc_trans_omp_parallel,

Re: Implement C _FloatN, _FloatNx types [version 6]

On 17/08/16 21:17, Joseph Myers wrote: > Although there is HFmode support for ARM and AArch64, use of that for > _Float16 is not enabled. Supporting _Float16 would require additional > work on the excess precision aspects of TS 18661-3: there are new > values of FLT_EVAL_METHOD, which are not

[Bug c++/77297] New: -Wnonnull-compare not emitted inside ternary operator

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77297 Bug ID: 77297 Summary: -Wnonnull-compare not emitted inside ternary operator Product: gcc Version: 6.1.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c++/77298] New: -Wnonnull-compare only emitted for code which is invoked

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77298 Bug ID: 77298 Summary: -Wnonnull-compare only emitted for code which is invoked Product: gcc Version: 6.1.0 Status: UNCONFIRMED Severity: normal

[Bug c++/77299] New: No warning for unused "INT64_MAX" and similar constants

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77299 Bug ID: 77299 Summary: No warning for unused "INT64_MAX" and similar constants Product: gcc Version: 6.1.0 Status: UNCONFIRMED Severity: normal

Re: PING: new pass to warn on questionable uses of alloca() and VLAs

On 08/04/2016 12:37 PM, Jeff Law wrote: [ughhh, one more time but with actual content] On 07/27/2016 03:01 AM, Aldy Hernandez wrote: Just in case this got lost in noise, since I know there was a lot of back and forth between Martin Sebor and I. This is the last iteration. Tested on x86-64

Re: PING: new pass to warn on questionable uses of alloca() and VLAs

On 08/19/2016 05:35 AM, Aldy Hernandez wrote: On 08/04/2016 12:37 PM, Jeff Law wrote: On 07/27/2016 03:01 AM, Aldy Hernandez wrote: Just in case this got lost in noise, since I know there was a lot of back and forth between Martin Sebor and I. This is the last iteration. Tested on x86-64

Re: Implement C _FloatN, _FloatNx types [version 6]

On Fri, 19 Aug 2016, Richard Biener wrote: > >> Can you quickly verify if LTO works with the new types? I don't see > >> anything > >> that would prevent it but having new global trees and backends > >> initializing them > >> might come up with surprises (see

Re: [ARM][PR target/77281] Fix an invalid check for vectors of, the same floating-point constants.

On 19/08/16 15:06, Matthew Wahab wrote: > On 19/08/16 14:30, Richard Earnshaw (lists) wrote: >> On 19/08/16 12:48, Matthew Wahab wrote: >>> 2016-08-19 Matthew Wahab >>> >>> PR target/77281 >>> * config/arm/arm.c (neon_valid_immediate): Delete declaration. >>>

Re: [PATCH] Add a TARGET_GEN_MEMSET_VALUE hook

On Fri, Aug 19, 2016 at 2:21 AM, Richard Biener wrote: > On Thu, Aug 18, 2016 at 5:16 PM, H.J. Lu wrote: >> On Thu, Aug 18, 2016 at 1:18 AM, Richard Biener >> wrote: >>> On Wed, Aug 17, 2016 at 10:11 PM, H.J. Lu

Re: Repeated use of the OpenACC routine directive

On 08/16/2016 06:05 PM, Thomas Schwinge wrote: > On Mon, 01 Aug 2016 17:51:24 +0200, I wrote: >> > We found that it's not correct that we currently unconditionally diagnose >> > an error for repeated use of the OpenACC routine directive on one >> > function/declaration. (For reference, it is also

[Bug fortran/77296] Compiler Error with allocatable string and associate

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77296 --- Comment #1 from Thomas Koenig --- Also fails with 5.4.0.

Re: [ARM][PR target/77281] Fix an invalid check for vectors of, the same floating-point constants.

On 19/08/16 14:30, Richard Earnshaw (lists) wrote: On 19/08/16 12:48, Matthew Wahab wrote: 2016-08-19 Matthew Wahab PR target/77281 * config/arm/arm.c (neon_valid_immediate): Delete declaration. Use const_vec_duplicate to check for duplicated elements.

[Bug target/77281] [ARM] Wrong code generated for move of constant vector with mix of signed and unsigned zeros

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77281 --- Comment #2 from mwahab at gcc dot gnu.org --- Author: mwahab Date: Fri Aug 19 13:59:18 2016 New Revision: 239610 URL: https://gcc.gnu.org/viewcvs?rev=239610=gcc=rev Log: [ARM] Fix an invalid check for vectors of the same floating-point

Re: [ARM][PR target/77281] Fix an invalid check for vectors of, the same floating-point constants.

On 19/08/16 12:48, Matthew Wahab wrote: > Hello, > > Test gcc.c-torture/execute/ieee/pr72824-2.c fails for arm targets > because the code generated to move a vector of signed and unsigned zeros > treats it as a vector of unsigned zeros. > > That is, an assignment x = { 0.f, -0.f, 0.f, -0.f } is

[Bug middle-end/71065] Missing diagnostic for statements between OpenMP 'target' and 'teams'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71065 --- Comment #2 from Jakub Jelinek --- Note that according to the omp-lang discussions #pragma omp target { #pragma omp teams { ... } } is fine, while even #pragma omp target { {} #pragma omp teams { ... } } (or ; etc., before

  1   2   >