[PATCH 4/4] (v2) Add -fdiagnostics-generate-patch

Changed in v2: I dropped -fdiagnostics-apply-fixits This patch uses the edit_context machinery to provide a new -fdiagnostics-generate-patch option. If set an edit_context is created for global_dc, and any fix-it hints emitted by diagnostics are added to the edit_context.

[PATCH 0/4] (v2) Generating patches from fix-it hints

Here's a much less ambitious version of the patch kit, which eliminates any attempt to write to the user's source code (getting rid of edit_context::apply_changes and -fdiagnostics-apply-fixits). It implements -fdiagnostics-generate-patch. In so doing, it tightens up the exact semantics of

[PATCH 2/4] Improvements to typed_splay_tree

This patch adds foreach, max and min methods to class typed_splay_tree, along with the start of a selftest suite. gcc/ChangeLog: * Makefile.in (OBJS): Add typed-splay-tree.o. * selftest-run-tests.c (selftest::run_tests): Call typed_splay_tree_c_tests. * selftest.h

[PATCH 3/4] (v2) Introduce class edit_context

This version removes edit_context::apply_changes and related functionality, retaining the ability to generate diffs. It also improves error-handling (adding a selftest for this). gcc/ChangeLog: * Makefile.in (OBJS-libcommon): Add edit-context.o. * diagnostic-color.c (color_dict):

[PATCH 1/4] selftest: split out named_temp_file from temp_source_file

Split out a new base class for temp_source_file, named_temp_file, moving the deletion to the base class dtor, so that we can write out temporary files in other ways in selftests. gcc/ChangeLog: * selftest.c (selftest::named_temp_file::named_temp_file): New ctor.

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

>> --Wno-format-contains-nul -Wno-format-extra-args -Wformat-nonliteral @gol >> +-Wno-format-contains-nul -Wno-format-extra-args -Wformat-length=1 @gol >> >> Most options that take levels are documented as: >> >> -Wshift-overflow -Wshift-overflow=@var{n} >> -Wstrict-overflow

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

On 08/24/2016 04:03 PM, Joseph Myers wrote: On Wed, 24 Aug 2016, Martin Sebor wrote: No. I recall having seen Glibc fail with ENOMEM years ago when formatting a floating point number to a very large precision but I haven't seen any implementation fail. I haven't yet looked to see if the

Re: [PATCH 1/4][PR 71931] Fix libatomic tests

On Wed, 24 Aug 2016, Szabolcs Nagy wrote: > diff --git a/libatomic/testsuite/lib/libatomic.exp > b/libatomic/testsuite/lib/libatomic.exp > index cafab54..e374c64 100644 > --- a/libatomic/testsuite/lib/libatomic.exp > +++ b/libatomic/testsuite/lib/libatomic.exp > @@ -47,6 +47,8 @@ load_gcc_lib

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

On Wed, 24 Aug 2016, Martin Sebor wrote: > No. I recall having seen Glibc fail with ENOMEM years ago when > formatting a floating point number to a very large precision but > I haven't seen any implementation fail. I haven't yet looked to > see if the Glibc failure can still happen. My reading

Re: [PATCH 0/4] Applying fix-its on behalf of the user to their code

On 24/08/16 14:56, Richard Biener wrote: You never typoed gcc t.c -o t.c ? ;) (I did ... :/) With GCC >=5 $ gcc t.c -o t.c gcc: fatal error: input file ‘t.c’ is the same as output file compilation terminated. You are welcome ;-) Manuel.

Re: C PATCH to suppress a bogus "defaulting to int" warning (PR c/77323)

On Wed, 24 Aug 2016, Marek Polacek wrote: > 2016-08-24 Marek Polacek > > PR c/77323 > * c-decl.c (declspecs_add_type): Set typespec_word even when __intN > or _FloatN or _FloatNx is not supported. > (finish_declspecs): Set type to integer_type_node

Re: [PATCH, Fortran] Fix compare logic for anonymous structure types

https://gcc.gnu.org/ml/fortran/2016-08/msg00144.html On Wed, Aug 24, 2016 at 5:14 PM, Fritz Reese wrote: > With a few recent notes by others, I have identified that the > comparison logic I used in interface.c (compare_components, > gfc_compare_derived_types) was faulty in

[PATCH, Fortran] Fix compare logic for anonymous structure types

With a few recent notes by others, I have identified that the comparison logic I used in interface.c (compare_components, gfc_compare_derived_types) was faulty in a few ways. I apologize in advance for the length of this message, but I believe it will help others (and myself) understand (recall)

Re: [PATCH] check -nopie in configure

onsdag 24 augusti 2016 kl. 18:21:07 CEST skrev Szabolcs Nagy: > On 20/07/16 14:58, Szabolcs Nagy wrote: > > since gcc can be built with --enable-default-pie, there > > is a -no-pie flag to turn off PIE. > > > > gcc cannot be built as PIE (pr 71934), so the gcc build > > system has to detect the

Re: Add fixit hint for -Wlogical-not-parentheses

On Wed, 2016-08-24 at 21:50 +0200, Marek Polacek wrote: > On Wed, Aug 24, 2016 at 02:59:43PM -0400, David Malcolm wrote: > > On Wed, 2016-08-24 at 20:15 +0200, Marek Polacek wrote: > > > On Wed, Aug 24, 2016 at 01:57:15PM -0400, David Malcolm wrote: > > > > On Wed, 2016-08-24 at 19:43 +0200, Marek

Re: Add fixit hint for -Wlogical-not-parentheses

On Wed, Aug 24, 2016 at 02:59:43PM -0400, David Malcolm wrote: > On Wed, 2016-08-24 at 20:15 +0200, Marek Polacek wrote: > > On Wed, Aug 24, 2016 at 01:57:15PM -0400, David Malcolm wrote: > > > On Wed, 2016-08-24 at 19:43 +0200, Marek Polacek wrote: > > > > This patch adds a fixit hint to

Re: [Patch, libstdc++/77356] Support escape in regex bracket expression

On Wed, Aug 24, 2016 at 1:41 AM, Jonathan Wakely wrote: > On 24/08/16 00:18 -0700, Tim Shen wrote: >> >> I didn't realized that we can actually escape a dash inside bracket >> expression: R"([\-])", in which case the dash should be treated >> literally. > > > With this patch

Re: [Patch, fortran] pr77358 - [F08] deferred-length character function returns zero-length string

...and to 6-branch as revision 239741. Cheers Paul On 24 August 2016 at 21:41, Paul Richard Thomas wrote: > Dear Tobias, > > Committed to trunk as revision 239740. 6-branch to follow. > > Thanks for the review. > > Best regards > > Paul -- The difference

Re: [Patch, fortran] pr77358 - [F08] deferred-length character function returns zero-length string

Dear Tobias, Committed to trunk as revision 239740. 6-branch to follow. Thanks for the review. Best regards Paul

[PATCH][mips] Add support for mips*r6-*-musl

Add the musl dynamic linker names for mips r6. It seems DRIVER_SELF_SPECS sets the default mips isa (MIPS_DEFAULT_ISA_LEVEL_SPEC) on *-mti-linux* or *-mti-elf, but not on gnu linux targets (see config/mips/mti-linux.h vs config/mips/gnu-user.h). Is that ok? It seems broken, but i didn't try to

[PATCH][mips] Fix linux header use in libgcc

gcc should use libc headers, not kernel headers. libgcc/ 2016-08-24 Szabolcs Nagy * config/mips/linux-unwind.h: Use sys/syscall.h. diff --git a/libgcc/config/mips/linux-unwind.h b/libgcc/config/mips/linux-unwind.h index bf12de5..4035c121 100644 ---

[PATCH 3/4][PR 71931] Fix libitm tests

Pass build time CC make var down to dejagnu so the sysroot is set correctly when gcc is built with --with-build-sysroot. libitm/ 2016-08-24 Szabolcs Nagy PR testsuite/71931 * configure.ac: Add AC_CONFIG_FILES. * configure: Regenerated. *

[PATCH 2/4][PR 71931] Fix libgomp tests

Pass build time CC make var down to dejagnu so the sysroot is set correctly when gcc is built with --with-build-sysroot. Existing libgomp-test-support.exp.in machinery is used. libgomp/ 2016-08-23 Szabolcs Nagy PR testsuite/71931 *

[PATCH 1/4][PR 71931] Fix libatomic tests

Pass build time CC make var down to dejagnu so the sysroot is set correctly when gcc is built with --with-build-sysroot. libatomic/ 2016-08-24 Szabolcs Nagy PR testsuite/71931 * configure.ac: Add AC_CONFIG_FILES. * configure: Regenerated.

[PATCH 0/4][PR 71931] Fix target lib tests --with-build-sysroot

The dejagnu find_gcc function cannot handle if CC needs extra flags like --sysroot. So for testing target libraries use the same CC that was used for building the target libs. New patch works even if runtest is not invoked from make as discussed

Re: Add fixit hint for -Wlogical-not-parentheses

On Wed, 2016-08-24 at 20:15 +0200, Marek Polacek wrote: > On Wed, Aug 24, 2016 at 01:57:15PM -0400, David Malcolm wrote: > > On Wed, 2016-08-24 at 19:43 +0200, Marek Polacek wrote: > > > This patch adds a fixit hint to -Wlogical-not-parentheses. When > > > the > > > LHS > > > has a location, it

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

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

[PATCH, PR70955] Tag {ms,sysv}_va_list_type_node with {ms,sysv}_abi attribute

Hi, in PR70955, ix86_canonical_va_list_type fails to recognize a __builtin_ms_va_list that was declared in a TU, because its type doesn't have the same main variant as the ms_va_list_type_node initialized in lto1. This patch fixes the PR by tagging ms_va_list_type_node and

Re: Add fixit hint for -Wlogical-not-parentheses

On Wed, Aug 24, 2016 at 01:57:15PM -0400, David Malcolm wrote: > On Wed, 2016-08-24 at 19:43 +0200, Marek Polacek wrote: > > This patch adds a fixit hint to -Wlogical-not-parentheses. When the > > LHS > > has a location, it prints: > > > > z.c: In function ‘int foo(int, int)’: > > z.c:12:11:

Re: Add fixit hint for -Wlogical-not-parentheses

On Wed, 2016-08-24 at 19:43 +0200, Marek Polacek wrote: > This patch adds a fixit hint to -Wlogical-not-parentheses. When the > LHS > has a location, it prints: > > z.c: In function ‘int foo(int, int)’: > z.c:12:11: warning: logical not is only applied to the left hand side > of comparison

Re: [RS6000] ABI_V4 ifunc

On Wed, 24 Aug 2016, Alan Modra wrote: > Given a hidden visibility function declaration, the toolchain can say > that the function is local to the module. This generally means that a > call to the function can be direct, ie. doesn't need to go via the PLT > even in a shared library. However,

Add fixit hint for -Wlogical-not-parentheses

This patch adds a fixit hint to -Wlogical-not-parentheses. When the LHS has a location, it prints: z.c: In function ‘int foo(int, int)’: z.c:12:11: warning: logical not is only applied to the left hand side of comparison [-Wlogical-not-parentheses] r += !a == b; ^~ z.c:12:8: note:

Fix bogus warning with -Wlogical-not-parentheses (PR c/77292)

The -Wlogical-not-parentheses deliberately doesn't warn when the RHS has boolean type. But since in C the type of a comparison is int, we need to check for tcc_comparison, too. Bootstrapped/regtested on x86_64-linux and ppc64le-redhat-linux, ok for trunk? 2016-08-24 Marek Polacek

Re: [PATCH] check -nopie in configure

On 20/07/16 14:58, Szabolcs Nagy wrote: > since gcc can be built with --enable-default-pie, there > is a -no-pie flag to turn off PIE. > > gcc cannot be built as PIE (pr 71934), so the gcc build > system has to detect the -no-pie flag to disable PIE. > > historically default pie toolchains used

Re: [PATCH] report supported function classes correctly on *-musl

On 20/07/16 14:39, Szabolcs Nagy wrote: > All function classes listed in gcc/coretypes.h are supported by musl. > > Most of the optimizations based on these function classes are not > relevant for standard conform c code, but this is required to get > rid of some test system noise. > > gcc/ >

Re: [PATCH] disable ifunc on *-musl by default

On 20/07/16 14:37, Szabolcs Nagy wrote: > Musl libc does not support gnu ifunc, so disable it by default. > (not disabled on s390-* since that has no musl support yet.) > > gcc/ > 2016-07-20 Szabolcs Nagy > > * config.gcc (*-*-*musl*): Disable

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

On 08/23/2016 05:00 PM, Joseph Myers wrote: Some observations: * Does -fprintf-return-value allow for the possibility of snprintf failing because of a memory allocation failure and so returning -1 when GCC computed bounds on what it could return if successful? No. I recall having seen Glibc

New Ukrainian 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 Ukrainian team of translators. The file is available at: http://translationproject.org/latest/gcc/uk.po (This file, 'gcc-6.2.0.uk.po', has

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

Ping x2. On Wed, Aug 03, 2016 at 07:05:34PM -0500, Segher Boessenkool wrote: > Ping. > > > Segher > > > On Mon, Aug 01, 2016 at 01:42:37AM +, Segher Boessenkool wrote: > > This is the second version. Concern was renamed to component, and all > > other comments were addressed (I hope).

Re: wwwdocs: gcc-7/changes.html

On 23/08/16 21:54, Gerald Pfeifer wrote: On Tue, 23 Aug 2016, Segher Boessenkool wrote: I'm committing the following to wwwdocs as obvious. Thank you, Segher! That would have been my late evening program for today, otherwise. ;-) Thanks for doing this. Can we also add a link to this from

[wwwdocs] [PATCH] Add my changes to gcc-7/changes.html

This covers my changes so far for gcc 7, based on git log --author=dmalcolm \ 002c3f2881626f4dea765f89e4a11be1f4bac240..c3e800b980fb13f42468ceeaf723 a39f4cee0f3e Validates as XHTML 1.0 Transitional. OK to commit? (I don't have a working copy of mhc, so I can't easily test the CSS markup)

Re: Implement -Wimplicit-fallthrough (version 5)

I'm curious why this function takes the first argument by const reference when the function above by const pointer. Is there a subtle difference between the functions that I'm not seeing? For that matter, is there a convention in GCC? (FWIW, my own rule of thumb is to have a function take a

[PATCH][ARM] Refactor MOVW/MOVT fusion logic to allow extension

Hi all, If we want to add more macro fusion cases in the arm backend we need to rework the aarch_macro_fusion_pair_p a bit to not return early during the MOVW/MOVT fusion checks. This simple patch does that by adding a helper function that can be called with the two sets to check if they

Re: [Patch, fortran] PR48298 - [F03] User-Defined Derived-Type IO (DTIO)

Here is an additional test case demonstrating recursive calls. Regards, Jerry ! { dg-do run } ! ! Functional test of User Defined Derived Type IO. ! ! This tests recursive calls where a derived type has a member that is ! itself. ! MODULE p USE ISO_FORTRAN_ENV TYPE :: person CHARACTER

[PATCH, testsuite]: Improve and clean-up tree-ssa/prefetch-?.c testcases

Hello! Attached patch improves and cleans up tree-ssa/prefetch-? testcases in several ways: a) Enables testcases on 64bit x86 targets by selecting amdfam10 architecture instead of 32bit-only athlon architecture b) Removes unnecessary -msse2 -mfpmath=sse compile flags c) Removes unnecessary SSE2

[gomp4] Frame propagation for routines

I've committed this to the gomp4 branch. It addresses an issue I was puzzled we'd not met, but then I realized I'd been turning the optimizer on and thus inlining things, which hid the problem. If we pass a reference (i.e. addressof) a frame object to an openecc routine that itself contains

Re: [PATCH 0/4] Applying fix-its on behalf of the user to their code

On Wed, Aug 24, 2016 at 3:45 PM, Bernd Schmidt wrote: > On 08/24/2016 03:28 AM, David Malcolm wrote: > >> (B) -fdiagnostics-apply-fixits, which writes back the changes >> to the input files. > > > That sounds really scary, there's no way I'd personally ever enable > something

Re: Implement -Wimplicit-fallthrough (version 5)

On Mon, Aug 22, 2016 at 10:31:16AM -0600, Martin Sebor wrote: > Just a few minor nits based on a quick reading of the patch: Thanks for looking into this. > > @@ -24114,6 +24164,16 @@ cp_parser_std_attribute (cp_parser *parser) > > " use %"); > >

Re: [PATCH 0/4] Applying fix-its on behalf of the user to their code

On 08/24/2016 03:28 AM, David Malcolm wrote: (B) -fdiagnostics-apply-fixits, which writes back the changes to the input files. That sounds really scary, there's no way I'd personally ever enable something like this. Do we have any data about what percentage of fixits actually correctly

Re: [PATCH 0/4] Various GCOV/PGO improvements

Martin and Jan, This set of patches introduces a huge number of testsuite regressions on AIX. AIX defaults to 32 bit. Although it supports a 64 bit "long long" type, it does not have 64 bit atomic operations on "long long" in 32 bit mode. All of the testcases fails with ld: 0711-317 ERROR:

Re: [PATCH 0/4] Applying fix-its on behalf of the user to their code

On Wed, 2016-08-24 at 09:59 +0200, Richard Biener wrote: > On Wed, Aug 24, 2016 at 3:28 AM, David Malcolm > wrote: > > Currently our diagnostics subsystem can emit fix-it hints > > suggesting edits the user can make to their code to fix > > warnings/errors, > > but currently

Re: [PATCH 0/4] Applying fix-its on behalf of the user to their code

On Wed, Aug 24, 2016 at 09:59:18AM +0200, Richard Biener wrote: > On Wed, Aug 24, 2016 at 3:28 AM, David Malcolm wrote: > > Currently our diagnostics subsystem can emit fix-it hints > > suggesting edits the user can make to their code to fix warnings/errors, > > but currently

Re: [PATCH 0/4] Applying fix-its on behalf of the user to their code

On Tue, 2016-08-23 at 21:57 -0400, Eric Gallager wrote: > On 8/23/16, David Malcolm wrote: > > Currently our diagnostics subsystem can emit fix-it hints > > suggesting edits the user can make to their code to fix > > warnings/errors, > > but currently the user must make these

Re: [PATCH 2/2][v4] Drop excess size used for run time allocated stack variables.

On Wed, Aug 24, 2016 at 7:42 AM, Andreas Krebbel wrote: > On 08/24/2016 04:02 AM, David Edelsohn wrote: >> This patch broke bootstrap on AIX. Stage1 GCC is miscompiled. >> >> Please revert this patch. > > Done. Sorry for the breakage. Is the alignment assumption

Re: [Patch, fortran] pr77358 - [F08] deferred-length character function returns zero-length string

Dear Paul, Paul Richard Thomas wrote: > The attached fixes this problem, bootstraps and regtests on FC21/x86_64. > OK for 6-branch and trunk? Looks good to me. Thanks for the patch. Tobias > 2016-08-24 Paul Thomas > > PR fortran/77358 > > * resolve.c

Re: [RFC] ipa bitwise constant propagation

On 22 August 2016 at 19:24, Prathamesh Kulkarni wrote: > On 22 August 2016 at 19:03, Martin Jambor wrote: >> Hi, >> >> On Tue, Aug 16, 2016 at 06:34:48PM +0530, Prathamesh Kulkarni wrote: >>> Thanks, I updated the patch to address these issues

[Patch, fortran] pr77358 - [F08] deferred-length character function returns zero-length string

Dear All, The attached fixes this problem, bootstraps and regtests on FC21/x86_64. OK for 6-branch and trunk? Paul 2016-08-24 Paul Thomas PR fortran/77358 * resolve.c (resolve_fl_procedure): Use the correct gfc_charlen for deferred character length module

Re: [PATCH] Add a TARGET_GEN_MEMSET_VALUE hook

On Mon, Aug 22, 2016 at 5:28 PM, H.J. Lu wrote: > On Mon, Aug 22, 2016 at 4:31 AM, Richard Biener > wrote: >> On Fri, Aug 19, 2016 at 4:45 PM, H.J. Lu wrote: >>> On Fri, Aug 19, 2016 at 2:21 AM, Richard Biener >>>

Re: [PATCH 2/2][v4] Drop excess size used for run time allocated stack variables.

On 08/24/2016 04:02 AM, David Edelsohn wrote: > This patch broke bootstrap on AIX. Stage1 GCC is miscompiled. > > Please revert this patch. Done. Sorry for the breakage. -Andreas-

Re: [PR49366] emit loc exprs for C++ non-virtual pmf template value parms

On Sat, Jul 23, 2016 at 4:30 PM, Alexandre Oliva wrote: > We used to emit, in debug information, the values bound to pointer to > member function template parameters only when they were NULL or > virtual member functions, because those can be represented with >

Re: Weird behaviour with --target_board="unix{var1,var2}"

On 23/08/16 12:05 +0100, Pedro Alves wrote: On 08/23/2016 10:54 AM, Jonathan Wakely wrote: That's being set by prettyprinters.exp and xmethods.exp (so it's GDB's fault! ;-) :-) This seems to work. I'll do some more testing and commit later today. LGTM. Though IME, save/restoring globals

Re: [PATCH 0/7, GCC, V8M] ARMv8-M Security Extensions

On 10/08/16 09:08, Andre Vieira (lists) wrote: > On 09/08/16 17:47, Sandra Loosemore wrote: >> On 08/09/2016 06:01 AM, Andre Vieira (lists) wrote: >>> [snip] >>> >>> The documentation is in the ARMV8-M Security Extensions in: ARM®v8-M >>> Security Extensions: Requirements on Development Tools

[PATCHv2 6/7, GCC, ARM, V8M] ARMv8-M Security Extension's cmse_nonsecure_call: use __gnu_cmse_nonsecure_call

On 25/07/16 14:26, Andre Vieira (lists) wrote: > This patch extends support for the ARMv8-M Security Extensions > 'cmse_nonsecure_call' to use a new library function > '__gnu_cmse_nonsecure_call'. This library function is responsible for > (without using r0-r3 or d0-d7): > 1) saving and clearing

[PATCHv2 5/7, GCC, ARM, V8M] Handling ARMv8-M Security Extension's cmse_nonsecure_call attribute

On 25/07/16 14:25, Andre Vieira (lists) wrote: > This patch adds support for the ARMv8-M Security Extensions > 'cmse_nonsecure_call' attribute. This attribute may only be used for > function types and when used in combination with the '-mcmse' > compilation flag. See Section 5.5 of ARM®v8-M

Re: [PATCH 7/7, GCC, ARM, V8M] Added support for ARMV8-M Security Extension cmse_nonsecure_caller intrinsic

On 25/07/16 14:28, Andre Vieira (lists) wrote: > This patch adds support ARMv8-M's Security Extension's > cmse_nonsecure_caller intrinsic. This intrinsic is used to check whether > an entry function was called from a non-secure state. > See Section 5.4.3 of ARM®v8-M Security Extensions:

[PATCHv2 4/7, GCC, ARM, V8M] ARMv8-M Security Extension's cmse_nonsecure_entry: clear registers

On 25/07/16 14:23, Andre Vieira (lists) wrote: > This patch extends support for the ARMv8-M Security Extensions > 'cmse_nonsecure_entry' attribute to safeguard against leak of > information through unbanked registers. > > When returning from a nonsecure entry function we clear all caller-saved >

[PATCHv2 2/7, GCC, ARM, V8M] Handling ARMv8-M Security Extension's cmse_nonsecure_entry attribute

On 25/07/16 14:21, Andre Vieira (lists) wrote: > This patch adds support for the ARMv8-M Security Extensions > 'cmse_nonsecure_entry' attribute. In this patch we implement the > attribute handling and diagnosis around the attribute. See Section 5.4 > of ARM®v8-M Security Extensions >

[PATCHv2 1/7, GCC, ARM, V8M] Add support for ARMv8-M's Secure Extensions flag and intrinsics

On 25/07/16 14:19, Andre Vieira (lists) wrote: > This patch adds the support of the '-mcmse' option to enable ARMv8-M's > Security Extensions and supports the following intrinsics: > cmse_TT > cmse_TT_fptr > cmse_TTT > cmse_TTT_fptr > cmse_TTA > cmse_TTA_fptr > cmse_TTAT > cmse_TTAT_fptr >

Re: C PATCH to suppress a bogus "defaulting to int" warning (PR c/77323)

On Wed, Aug 24, 2016 at 12:18:17PM +0200, Marek Polacek wrote: > When declaring something using an unsupported type specifier, such as __int128 > on 32-bit systems, or _Float128x, the error for the unsupported type is > followed by a warning about the type defaulting to int. > > But for

C PATCH to suppress a bogus "defaulting to int" warning (PR c/77323)

When declaring something using an unsupported type specifier, such as __int128 on 32-bit systems, or _Float128x, the error for the unsupported type is followed by a warning about the type defaulting to int. But for unsupported types this warning isn't useful. The problem was that for these

Re: [patch] [gsoc] [gimplefe] GIMPLE FE Project

On Mon, Aug 22, 2016 at 8:40 PM, Prasad Ghangal wrote: > On 22 August 2016 at 16:55, Trevor Saunders wrote: >> On Sun, Aug 21, 2016 at 10:35:17PM +0530, Prasad Ghangal wrote: >>> Hi all, >>> >>> As a part of my gsoc project. I have completed the

Re: Fwd: [PATCH] genmultilib: improve error reporting for MULTILIB_REUSE

On 18/08/16 17:39, Jeff Law wrote: On 08/10/2016 09:51 AM, Thomas Preudhomme wrote: *** gcc/ChangeLog *** 2016-08-01 Thomas Preud'homme * doc/fragments.texi (MULTILIB_REUSE): Mention that only options in MULTILIB_OPTIONS should be used. Small

Re: [PATCH, ARM] Fix aprofile multilib mappings

On 24/08/16 09:13, Ramana Radhakrishnan wrote: On 10/08/16 14:28, Thomas Preudhomme wrote: Hi, Mappings (MULTILIB_MATCHES and MULTILIB_REUSE) in ARM aprofile multilib suffer from a number of issues: * missing mapping of -mcpu=cortex-a7 to -march=armv7-a You mean -march=armv7ve... Yes

New template for 'gcc' made available

Hello, gentle maintainer. This is a message from the Translation Project robot. (If you have any questions, send them to .) A new POT file for textual domain 'gcc' has been made available to the language teams for translation. It is archived as:

Re: [patch] [gsoc] [gimplefe] GIMPLE FE Project

On Wed, Aug 24, 2016 at 9:02 AM, Prasad Ghangal wrote: > On 23 August 2016 at 21:15, Prasad Ghangal wrote: >> On 23 August 2016 at 02:56, David Malcolm wrote: >>> On Tue, 2016-08-23 at 00:10 +0530, Prasad Ghangal wrote:

[Patch, testsuite] Fix more bogus test failures for avr

Hi, This patch fixes a couple of testsuite failures for the avr target by requiring int32plus support for zero_sign_ext_test.c, and explicitly using __UINT32_TYPE__ instead of assuming 32 bit ints for pr71083.c Regtested with avr and x86_64-pc-linux. Committed to trunk. Regards Senthil

Re: [Patch, libstdc++/77356] Support escape in regex bracket expression

On 24/08/16 00:18 -0700, Tim Shen wrote: I didn't realized that we can actually escape a dash inside bracket expression: R"([\-])", in which case the dash should be treated literally. With this patch applied I no longer get a match for: regex_match("-", std::regex{"[a-]",

Re: [PATCH, ARM] Fix aprofile multilib mappings

On 10/08/16 14:28, Thomas Preudhomme wrote: > Hi, > > Mappings (MULTILIB_MATCHES and MULTILIB_REUSE) in ARM aprofile multilib > suffer from a number of issues: > > * missing mapping of -mcpu=cortex-a7 to -march=armv7-a You mean -march=armv7ve... > * typo on vfpv3-d16-fp16 (MULTILIB_MATCHES

Re: [PATCH] Remove whitespace

On 22/08/16 23:38 +0100, Jonathan Wakely wrote: On 22/08/16 15:30 -0700, Mike Stump wrote: On Aug 22, 2016, at 2:45 PM, Aditya Kumar wrote: libstdc++-v3/ChangeLog | 5 + libstdc++-v3/include/bits/algorithmfwd.h| 206

Re: [PATCH 0/4] Applying fix-its on behalf of the user to their code

On Wed, Aug 24, 2016 at 3:28 AM, David Malcolm wrote: > Currently our diagnostics subsystem can emit fix-it hints > suggesting edits the user can make to their code to fix warnings/errors, > but currently the user must make these edits manually [1]. > > The following patch

RE: [PATCH 3/4] Add support to run auto-vectorization tests for multiple effective targets

Hi Jeff, > > The following patch reverts to the old behaviour. I also removed misleading > > comments and related logic that checks for the cached result. There might > > be > > other procedures with similar inconsistency but here I only modified the > offending ones. > Thanks. Given how much

RE: [PATCH 3/4] Add support to run auto-vectorization tests for multiple effective targets

> On 08/23/2016 04:15 PM, Trevor Saunders wrote: > > > > I've certainly been tempted to take a stab at at least replacing the > > expect stuff with something else, it drives me kind of crazy to see how > > much testsuite time is spent running expect. Even if we can't do all of > > it, the vast

[Patch, libstdc++/77356] Support escape in regex bracket expression

I didn't realized that we can actually escape a dash inside bracket expression: R"([\-])", in which case the dash should be treated literally. Tell me if you feel like we need more documentations. :P Bootstrapped and tested on x86_64-linux-gnu. Thanks! -- Regards, Tim Shen commit

Re: [patch] [gsoc] [gimplefe] GIMPLE FE Project

On 23 August 2016 at 21:15, Prasad Ghangal wrote: > On 23 August 2016 at 02:56, David Malcolm wrote: >> On Tue, 2016-08-23 at 00:10 +0530, Prasad Ghangal wrote: >>> On 22 August 2016 at 16:55, Trevor Saunders >>> wrote: >>> >

[PATCH, PR71602, 4/4] Make canonical_va_list_type more strict

[ was: Re: [PATCH, PR71602] Give error for invalid va_list argument to va_arg ] On 23/06/16 23:21, Jason Merrill wrote: On Thu, Jun 23, 2016 at 1:27 PM, Tom de Vries wrote: Hi, this patch fixes PR71602, a 6/7 regression. Consider this test-case:>> The patch fixes

[PATCH, 3/4] Fix assert in build_va_arg, case 2b

Hi, this patch fixes an assert in build_va_arg. Instead of testing for pointer equality, we use the same test as is used in std_canonical_va_list_type. Bootstrapped and reg-tested on x86_64. OK for trunk? Thanks, - Tom Fix assert in build_va_arg, case 2b 2016-08-22 Tom de Vries

[PATCH, 2/4] Replace error_at with assert in build_va_arg

Hi, at the start of build_va_arg, we error out if there's an invalid va_list argument. Therefore, the following checks on va_list type are not user errors, but internal errors. This patch changes the user errors into internal errors. Bootstrapped and reg-tested on x86_64. OK for trunk?