Re: Do not use TYPE_CANONICAL in useless_type_conversion

> There must be a reason why I allowed modes to differ there btw ;) Thinking about it, I guess reason is that incomplete types do not have resonable modes set, so requiring modes to match will prevent complete and incomplete types to match. Here is updated patch which uses the earlier mode check

Re: [patch] libstdc++/67747 Allocate space for dirent::d_name

On 02/10/15 14:16 +0200, Florian Weimer wrote: On 09/29/2015 01:37 PM, Jonathan Wakely wrote: POSIX says that dirent::d_name has an unspecified length, so calls to readdir_r must pass a buffer with enough trailing space for {NAME_MAX}+1 characters. I wasn't doing that, which works OK on

Re: [patch] libstdc++/67747 Allocate space for dirent::d_name

On 02/10/15 14:16, Florian Weimer wrote: On 09/29/2015 01:37 PM, Jonathan Wakely wrote: >POSIX says that dirent::d_name has an unspecified length, so calls to >readdir_r must pass a buffer with enough trailing space for >{NAME_MAX}+1 characters. I wasn't doing that, which works OK on

Re: [GCC, ARM] armv8 linux toolchain asan testcase fail due to stl missing conditional code

On 01/10/15 21:21, Christophe Lyon wrote: On 1 October 2015 at 11:10, Kyrill Tkachov wrote: On 30/09/15 17:39, Kyrill Tkachov wrote: On 09/06/15 09:17, Kyrill Tkachov wrote: On 05/06/15 14:14, Kyrill Tkachov wrote: On 05/06/15 14:11, Richard Earnshaw wrote: On

[SH][committed]

Hi, The attached SH patch converts sequences such as: movtr2 movtr13 into: movtr2 mov r2,r13 This shortens the live range of the T bit register and is better for parallel execution. It doesn't happen often, but it's easy to avoid it.

Re: Cache reals for 1/4, 1/6 and 1/9

On Thu, Oct 1, 2015 at 3:59 PM, Bernd Schmidt wrote: > On 10/01/2015 03:51 PM, Richard Sandiford wrote: >> >> We have a global 1/2 and a cached 1/3, but recalculate 1/4, 1/6 and 1/9 >> each time we need them. That seems a bit arbitrary and makes the folding >> code more

[Ada] Use more FOR_EACH_VEC_* macros

Tested on x86_64-suse-linux, applied on the mainline. 2015-10-02 Eric Botcazou * gcc-interface/trans.c (find_loop_for): Use FOR_EACH_VEC_ELT_REVERSE. (Loop_Statement_to_gnu): Use FOR_EACH_VEC_ELT. (finalize_nrv): Use FOR_EACH_VEC_SAFE_ELT and

Re: [PATCH] rs6000: Add "cannot_copy" attribute, use it (PR67788, PR67789)

On Fri, Oct 2, 2015 at 3:14 AM, Segher Boessenkool wrote: > On Fri, Oct 02, 2015 at 10:24:07AM +0930, Alan Modra wrote: >> On Thu, Oct 01, 2015 at 12:18:08PM -0500, Segher Boessenkool wrote: >> > On Thu, Oct 01, 2015 at 12:14:44PM +0200, Richard Biener wrote: >> > > So

Re: [Patch match.pd] Add a simplify rule for x * copysign (1.0, y);

On Fri, Oct 02, 2015 at 11:10:58AM +0200, Richard Biener wrote: > > BTW, it seems wrf also in many places uses MAX > > or MIN (always in pairs), would that be also > > something to optimize? > > Hmm, we'll already CSE copysign so the question is how to optimize > tem1 = MAX ; tem2= MIN

Re: [PATCH] fortran/67758 -- Prevent ICE caused by misplaced COMMON

Le 01/10/2015 18:30, Steve Kargl a écrit : I'm fine with your patch, although I find the error message to be somewhat confusing as no procedure appears in COMMON. Well, XX is implicitly a procedure. The call-stmt in the code is the start of an execution-construct. A common-stmt is not

Re: [Patch match.pd] Add a simplify rule for x * copysign (1.0, y);

On Fri, Oct 02, 2015 at 11:58:42AM +0200, Jakub Jelinek wrote: > On Fri, Oct 02, 2015 at 11:45:08AM +0200, Richard Biener wrote: > > > Note, I won't have time to work on this in the near future (OpenMP work > > > still on the plate), so if James (or anyone else?) has time for that, it > > > would

Re: [patch] libstdc++/67747 Allocate space for dirent::d_name

On 10/02/2015 02:37 PM, Sebastian Huber wrote: > > > On 02/10/15 14:16, Florian Weimer wrote: >> On 09/29/2015 01:37 PM, Jonathan Wakely wrote: >>> >POSIX says that dirent::d_name has an unspecified length, so calls to >>> >readdir_r must pass a buffer with enough trailing space for >>>

Re: [AArch64/testsuite] Add more TLS local executable testcases

Jiong Wang writes: > Marcus Shawcroft writes: > >> On 26 August 2015 at 14:58, Jiong Wang wrote: >>> >>> This patch cover tlsle tiny model tests, tls size truncation for tiny & >>> small model included also. >>> >>> All testcases pass native test. >>> >>> OK for trunk? >>>

Re: [PATCH, i386, AVX-512, doc] Mention all AVX-512 switches in invoke.texi.

On 01 Oct 17:51, Kirill Yukhin wrote: > `make pdf` looks ok. > Is it ok for trunk and gcc-5-branch (a week after check in to trunk)? > > gcc/ > * doc/invoke.texi: Mention -mavx512vl, -mavx512bw, -mavx512dq, > -mavx521vbmi, -mavx512ifma. Add missing opindex-es. Checked into main trunk.

Re: [Patch AArch64] Use default_elf_asm_named_section instead of special cased hook

On 2 October 2015 at 11:08, Ramana Radhakrishnan wrote: > * config/aarch64/aarch64-elf.h (TARGET_ASM_NAMED_SECTION): Use > default_elf_asm_named_section. > * config/aarch64/aarch64.c (aarch64_elf_asm_named_section): Delete. > --- >

Re: [PATCH] New attribute to create target clones

PING. On Fri, Sep 25, 2015 at 1:28 AM, Evgeny Stupachenko wrote: > I've fixed ICE and review issues. > x86 make check and bootstrap passed. > > Thanks, > Evgeny > > ChangeLog > > 2015-09-25 Evgeny Stupachenko > > gcc/ > * Makefile.in (OBJS): Add

Re: [PATCH, i386, AVX-512] Update extract_even_odd w/ AVX-512BW insns.

On 01 Oct 14:11, Kirill Yukhin wrote: > Bootstrapped. New tests pass (fail w/o the change). Regtesting is in progress. > > Is it ok for trunk? > > gcc/ > * config/i386/i386.c (expand_vec_perm_even_odd_trunc): New. > (expand_vec_perm_even_odd_1): Handle V64QImode. >

Re: [Patch AArch64] Use default_elf_asm_named_section instead of special cased hook

On 02/10/15 13:46, Marcus Shawcroft wrote: > On 2 October 2015 at 11:08, Ramana Radhakrishnan > wrote: > >> * config/aarch64/aarch64-elf.h (TARGET_ASM_NAMED_SECTION): Use >> default_elf_asm_named_section. >> * config/aarch64/aarch64.c

Re: [PATCH] SH FDPIC backend support

On Thu, 2015-10-01 at 21:30 -0400, Rich Felker wrote: > If you have any other general comments on the patch in the mean time > I'd be happy to hear them. Below are some comments. Might be a bit unstructured, I was hopping through the patch file. Sorry about that. > +function_symbol (rtx

[Boolean Vector, patch 2/5] Change vector comparison IL requirement

Hi, This patch change vector comparison to require boolean vector resulting type. Thanks, Ilya -- gcc/ 2015-10-02 Ilya Enkovich * tree-cfg.c (verify_gimple_comparison) Require boolean vector type for vector comparison.

[Boolean Vector, patch 4/5] Use boolean vectors in VEC_COND_EXPR

Hi, This patch forces boolean vector usage in VEC_COND_EXPR generated by vectorizer. VEC_COND_EXPR expand is fixed appropriately. Thanks, Ilya -- gcc/ 2015-10-02 Ilya Enkovich * optabs.c (expand_vec_cond_expr): Accept boolean vector as condition

Re: [patch] libstdc++/67747 Allocate space for dirent::d_name

On 10/02/2015 02:34 PM, Jonathan Wakely wrote: > On 02/10/15 14:16 +0200, Florian Weimer wrote: >> On 09/29/2015 01:37 PM, Jonathan Wakely wrote: >>> POSIX says that dirent::d_name has an unspecified length, so calls to >>> readdir_r must pass a buffer with enough trailing space for >>>

Re: [PATCH] x86 interrupt attribute

Hi, Here is a new patch. Added HJ's changes and review changes. Implement x86 interrupt attribute The interrupt and exception handlers are called by x86 processors. X86 hardware pushes information onto stack and calls the handler. The requirements are 1. Both interrupt and exception handlers

[wwwdocs] Mention -Wduplicated-cond

Applied. Index: changes.html === RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-6/changes.html,v retrieving revision 1.32 diff -u -r1.32 changes.html --- changes.html28 Sep 2015 00:43:48 - 1.32 +++ changes.html2 Oct

[Boolean Vector, patch 1/5] Introduce boolean vector to be used as a vector comparison type

Hi, This patch starts the first series to introduce vec as a vector comparison type. This series introduces the new vec type and force its usage for all vector comparisons. This series doesn't intoroduce any new vectorization features. I split it into five small patches but will commit in

Re: [AArch64/testsuite] Add more TLS local executable testcases

On 22 September 2015 at 17:49, Jiong Wang wrote: > 2015-09-22 Jiong Wang > > gcc/testsuite/ >* gcc.target/aarch64/tlsle12_tiny_1.c: New testcase for tiny model. >* gcc.target/aarch64/tlsle24_tiny_1.c: Likewise. >*

Re: [Patch AArch64] Use default_elf_asm_named_section instead of special cased hook

On 2 October 2015 at 14:01, Ramana Radhakrishnan wrote: >>> #undef TARGET_ASM_NAMED_SECTION >>> -#define TARGET_ASM_NAMED_SECTION aarch64_elf_asm_named_section >>> +#define TARGET_ASM_NAMED_SECTION default_elf_asm_named_section >> >> Isn't it sufficient to

[PATCH] Stop including in gcc/system.h

is deprecated on some systems and we gets hundreds of warnings due to including it on (at least) dragonfly and openbsd. We already do this earlier in system.h: #ifdef HAVE_STDLIB_H # include #endif /* When compiling C++ we need to include as well as so that it is processed before we

[Boolean Vector, patch 3/5] Use boolean vector in C/C++ FE

Hi, This patch makes C/C++ FE to use boolean vector as a resulting type for vector comparison. As a result vector comparison in source code now parsed into VEC_COND_EXPR, it required a testcase fix-up. Thanks, Ilya -- gcc/c 2015-10-02 Ilya Enkovich *

[[Boolean Vector, patch 5/5] Support boolean vectors in vector lowering

Hi, This patch supports boolean vectors in vector lowering. Main change is to lower vector comparison into comparisons, not cond_exprs. Thanks, Ilya -- 2015-10-02 Ilya Enkovich * tree-vect-generic.c (elem_op_func): Add new operand to hold vector

Re: [C/C++ PATCH] RFC: Implement -Wduplicated-cond (PR c/64249) (version 2)

On Wed, Sep 30, 2015 at 12:45:35PM -0600, Jeff Law wrote: > On 09/30/2015 09:47 AM, Joseph Myers wrote: > >The C front-end changes are OK. > The rest are OK as well. Thanks Jeff & Joseph. I'm going to apply the patch soon; should it draw the ire of users, I'll move the option to -Wextra.

Re: Do not describe -std=c11 etc. as experimental in c.opt help text

On 01.10.2015 19:01, Joseph Myers wrote: I noticed that c.opt still described -std=c11 and related options as experimental in the --help text. This patch fixes this. this seems to be true for the gcc-5 branch as well. Could you fix it there as well? Matthias

Re: [Patch match.pd] Add a simplify rule for x * copysign (1.0, y);

On Fri, Oct 02, 2015 at 10:18:01AM +0200, Richard Biener wrote: > On Thu, Oct 1, 2015 at 8:36 PM, Jakub Jelinek wrote: > > On Thu, Oct 01, 2015 at 02:57:15PM +0100, James Greenhalgh wrote: > >> 2015-10-01 James Greenhalgh > >> > >> * match.pd

[Fortran, committed] Fix ICE in string array constructor (pr 62242 & pr 52332)

Revision 228368... Louis

Re: [Patch match.pd] Add a simplify rule for x * copysign (1.0, y);

On Fri, Oct 02, 2015 at 11:06:53AM +0100, Marek Polacek wrote: > On Fri, Oct 02, 2015 at 11:58:42AM +0200, Jakub Jelinek wrote: > > On Fri, Oct 02, 2015 at 11:45:08AM +0200, Richard Biener wrote: > > > > Note, I won't have time to work on this in the near future (OpenMP work > > > > still on the

Re: Add a build_real_truncate helper function

On Thu, Oct 1, 2015 at 3:52 PM, Bernd Schmidt wrote: > On 10/01/2015 03:48 PM, Richard Sandiford wrote: >> >> ...which simplifies the match.pd patterns I'm about to add. >> >> Bootstrapped & regression-tested on x86_64-linux-gnu. OK to install? > > > Ok. I wonder if it's

Re: [Patch match.pd] Add a simplify rule for x * copysign (1.0, y);

On Fri, Oct 2, 2015 at 11:03 AM, Jakub Jelinek wrote: > On Fri, Oct 02, 2015 at 10:18:01AM +0200, Richard Biener wrote: >> On Thu, Oct 1, 2015 at 8:36 PM, Jakub Jelinek wrote: >> > On Thu, Oct 01, 2015 at 02:57:15PM +0100, James Greenhalgh wrote: >> >>

[Ada] Implement restricted aliasing for parameters

In Ada, parameters can be passed by reference or by copy and, for some types, the mechanism is specified by the language whereas, for other types, it's up to the implementation. In the former case, if the mechanism is by reference, full aliasing is allowed between parameters but, in the latter

[Ada] Remove linear search in Pragma_to_gnu

This shamelessly mimics what Manual implemented recently for the C family of compilers under PR c/49654 and PR c/49655. Tested on x86_64-suse-linux, applied on the mainline. 2015-10-02 Eric Botcazou * gcc-interface/trans.c (Pragma_to_gnu) : Replace

Re: Do not use TYPE_CANONICAL in useless_type_conversion

> I believe TYPE_ALIGN_OK should be "lowered" so that if you have a > handled-component chain with some intermediate TYPE_ALIGN_OK you > lower it to taking the address of that component and dereferencing > it (which is where the middle-end always trusts the alignment of > the type of the

[PR66776][PATCH][AARCH64] Add cmovdi_insn_uxtw pattern.

Hi all, This is a simple patch to add a new cmovdi_insn_uxtw rtx pattern to aarch64 backend. For the following simple test case: unsigned long long foo (unsigned int a, unsigned int b, unsigned int c) { return a ? b : c; } With this new pattern, the new code-generation will be: cmp

Re: [Patch match.pd] Add a simplify rule for x * copysign (1.0, y);

On Fri, Oct 2, 2015 at 12:24 PM, James Greenhalgh wrote: > On Fri, Oct 02, 2015 at 11:06:53AM +0100, Marek Polacek wrote: >> On Fri, Oct 02, 2015 at 11:58:42AM +0200, Jakub Jelinek wrote: >> > On Fri, Oct 02, 2015 at 11:45:08AM +0200, Richard Biener wrote: >> > > > Note,

Re: [PATCH] Improve DOM's optimization of control statements

Hi Jeff, Your patch causes an ICE regression. The test case is " gcc.c-torture/compile/pr27087.c", I observed it on aarch64-none-elf target when compiling the test case with '-Os' flag. A quick check shows, the cfg has been changed, but the loop information is not updated. Thus the

Re: [patch] libstdc++/67747 Allocate space for dirent::d_name

On 09/29/2015 01:37 PM, Jonathan Wakely wrote: > POSIX says that dirent::d_name has an unspecified length, so calls to > readdir_r must pass a buffer with enough trailing space for > {NAME_MAX}+1 characters. I wasn't doing that, which works OK on > GNU/Linux and BSD where d_name is a large array,

[Patch AArch64] Improve SIMD concatenation with zeroes

Hi, In AArch64, SIMD instructions which only touch the bottom 64-bits of a vector register write zeroes to the upper 64-bits. In other words, we have a cheap way to implement a "zero extend" of a SIMD operation, and can generate efficient code for: [(set (match_operand 0)

Re: [Patch AArch64] Improve SIMD concatenation with zeroes

On 02/10/15 09:12, James Greenhalgh wrote: 2015-10-01 James Greenhalgh * config/aarch64/aarch64-simd.md (*aarch64_combinez): Add alternatives for reads from memory and moves from general-purpose registers. (*aarch64_combinez_be):

[PATCH COMMITTED] MAINTAINERS (Write After Approval): Add myself.

I have just added myself. Index: ChangeLog === --- ChangeLog (revision 228379) +++ ChangeLog (working copy) @@ -1,3 +1,7 @@ +2015-10-02 Louis Krupp + + * MAINTAINERS (Write After Approval): Add

Re: [Patch match.pd] Add a simplify rule for x * copysign (1.0, y);

On Fri, Oct 2, 2015 at 11:27 AM, Jakub Jelinek wrote: > On Fri, Oct 02, 2015 at 11:10:58AM +0200, Richard Biener wrote: >> > BTW, it seems wrf also in many places uses MAX >> > or MIN (always in pairs), would that be also >> > something to optimize? >> >> Hmm, we'll already

[Patch AArch64] Use default_elf_asm_named_section instead of special cased hook

Hi, The hook for TARGET_ASM_NAMED_SECTION was defined separately in the backend around the time frame for GCC 4.7 under the assumption that '@' would be used as a comment character in the binutils port. This was indeed true in versions of the AArch64 port that never made it into the FSF tree.

[gomp4] Merge trunk r228315 (2015-10-01) into gomp-4_0-branch

Hi! Committed to gomp-4_0-branch in r228382: commit 519d8cb612e9d641d133e4f65b4a48c3ef963f43 Merge: 5094830 b5409c8 Author: tschwinge Date: Fri Oct 2 10:01:27 2015 + svn merge -r 228054:228315 svn+ssh://gcc.gnu.org/svn/gcc/trunk

[PATCH COMMITTED] Update MAINTAINERS

Just an email address update. Index: ChangeLog === --- ChangeLog (revision 228382) +++ ChangeLog (working copy) @@ -1,3 +1,7 @@ +2015-10-02 Florian Weimer + + * MAINTAINERS: Update email address. + 2015-10-02

Re: [Patch match.pd] Add a simplify rule for x * copysign (1.0, y);

On Thu, Oct 1, 2015 at 8:36 PM, Jakub Jelinek wrote: > On Thu, Oct 01, 2015 at 02:57:15PM +0100, James Greenhalgh wrote: >> 2015-10-01 James Greenhalgh >> >> * match.pd (mult (COPYSIGN:s real_onep @0) @1): New simplifier. > > Also, please note

[PATCH][AARCH64]Add csneg3_uxtw_insn pattern

Hi all, This is a simple patch to add csneg3_uxtw_insn into aarch64 backend. It will save one uxtw instruction as a write to the 32-bit w-register implicitly zero-extends the value up to the full 64 bits of an x-register. aarch64-none-elf regression test Okay without any issues. Okay to

Re: [Patch match.pd] Add a simplify rule for x * copysign (1.0, y);

On Fri, Oct 02, 2015 at 11:45:08AM +0200, Richard Biener wrote: > > Note, I won't have time to work on this in the near future (OpenMP work > > still on the plate), so if James (or anyone else?) has time for that, it > > would be greatly appreciated. > > So maybe just open an enhancement bug for

Re: [Patch match.pd] Add a simplify rule for x * copysign (1.0, y);

On Fri, Oct 02, 2015 at 11:24:32AM +0100, James Greenhalgh wrote: > > > PR67815. > > > > James, are you interested in this one, or would you prefer if I take it? > > I'm happy either way. > > I haven't looked at reassoc before, so I don't know my way wround it, and > I'm out of office for a

Re: [PATCH][AARCH64]Add csneg3_uxtw_insn pattern

On Fri, Oct 02, 2015 at 10:21:48AM +0100, Renlin Li wrote: > Hi all, > > This is a simple patch to add csneg3_uxtw_insn into aarch64 backend. It > will save one uxtw instruction as a write to the 32-bit w-register > implicitly > zero-extends the value up to the full 64 bits of an x-register. >

Re: [PR66776][PATCH][AARCH64] Add cmovdi_insn_uxtw pattern.

On Fri, Oct 02, 2015 at 10:17:11AM +0100, Renlin Li wrote: > Hi all, > > This is a simple patch to add a new cmovdi_insn_uxtw rtx pattern to > aarch64 backend. > > For the following simple test case: > > unsigned long long > foo (unsigned int a, unsigned int b, unsigned int c) > { >return

Re: [wwwdocs] Buildstat update for 5.x

On Sun, 13 Sep 2015, Tom G. Christensen wrote: > Testresults for 5.2.0: > i686-unknown-linux-gnu > powerpc-unknown-linux-gnu > sparc-sun-solaris2.10 > sparc64-sun-solaris2.10 > x86_64-unknown-linux-gnu (4) > x86_64-w64-mingw32 > > Testresults for 5.1.0: > hppa64-hp-hpux11.00

[gomp4.1] Unsigned long long doacross implementation

Hi! The default set of routines use long as the iterator type, if some loops need either unsigned long, or long long/unsigned long long, they need to use another implementation (__int128 iterators are not supported). This patch adds those entry points and fixes some issues on the compiler side.

Re: Add a build_real_truncate helper function

Richard Biener writes: > On Thu, Oct 1, 2015 at 3:52 PM, Bernd Schmidt wrote: >> On 10/01/2015 03:48 PM, Richard Sandiford wrote: >>> >>> ...which simplifies the match.pd patterns I'm about to add. >>> >>> Bootstrapped & regression-tested on

Re: Do not use TYPE_CANONICAL in useless_type_conversion

Hi, actually I do not quite understand why we need a TYPE_ALIGN_OK flag that is only used in Ada. Somehow other languages seem to have no problem of that kind. You remember, when I removed the TYPE_ALIGN_OK handing (initially it wasn't clear to me that it's entire use is only to make Ada

Re: [Patch, fortran] PR67721 deep copy missing when assigning derived type constructor to an array

On Sat, Sep 26, 2015 at 6:10 AM, Mikael Morin wrote: > Hello, > > I've just submitted this PR, and the patch as well, which passes the > testsuite. > > The problem is a missing deep copy when the rhs is a (scalar) derived type > constructor (with allocatable components) and

Re: Do not describe -std=c11 etc. as experimental in c.opt help text

On Thu, Oct 01, 2015 at 05:01:26PM +, Joseph Myers wrote: > I noticed that c.opt still described -std=c11 and related options as > experimental in the --help text. This patch fixes this. > > Jason, note that -std=gnu++11 and -std=gnu++14 still have that text, > contrary to the descriptions

Re: [C/C++ PATCH] RFC: Implement -Wduplicated-cond (PR c/64249) (version 2)

On Fri, Oct 2, 2015 at 3:23 AM, Marek Polacek wrote: > On Wed, Sep 30, 2015 at 12:45:35PM -0600, Jeff Law wrote: >> On 09/30/2015 09:47 AM, Joseph Myers wrote: >> >The C front-end changes are OK. >> The rest are OK as well. > > Thanks Jeff & Joseph. > > I'm going to apply the

Re: [PATCH] Cleanup of IPA-CP alignment lattices

> Hi, > > I have already proposed this patch many months ago but it got > forgotten, for a number of reasons. It does not change functionality, > it only cleans up the alignment lattices, which are currently a bit > clumsy. > > I have refreshed the patch and made sure it still bootstraps and

[PATCH] Reject loops early where ivs cannot be represented.

During scop detection we can figure out if loop IVs cannot be represeted in the polyhedral model. We now bail out early instead of waiting until graphite-sese-to-poly.c Passes regtest and bootstrap with BOOT_CFLAGS=="-g -O2 -fgraphite-identity -floop-nest-optimize" with ISL-0.15. gcc/ChangeLog:

Re: Do not use TYPE_CANONICAL in useless_type_conversion

> On Fri, 2 Oct 2015, Jan Hubicka wrote: > > > > There must be a reason why I allowed modes to differ there btw ;) > > > > Thinking about it, I guess reason is that incomplete types do not have > > resonable modes set, so requiring modes to match will prevent complete > > and incomplete types to

[PATCH] Disable -Wduplicated-cond for the time being

Given that the new warning currently breaks bootstrap [*] and I see no simple way how to resolve PR67819 derived out of the bootstrap failure, I'm moving -Wduplicated-cond out of -Wall and skipping one of the tests for the time being. I'm also reverting the hack in genemit.c. Oh well. [*]

[C PATCH] Another fix for missing diagnostics (PR c/67730)

This patch continues fixing up this PR, where we were failing to give diagnostics for attached testcases, because of NULL being defined in a system header. Probably the best we can do at this time is just to use expansion_point_location_if_in_system_header. That also means we will warn for

Re: Do not describe -std=c11 etc. as experimental in c.opt help text

On Fri, 2 Oct 2015, Matthias Klose wrote: > On 01.10.2015 19:01, Joseph Myers wrote: > > I noticed that c.opt still described -std=c11 and related options as > > experimental in the --help text. This patch fixes this. > > this seems to be true for the gcc-5 branch as well. Could you fix it

Re: [PATCH] SH FDPIC backend support

On Fri, Oct 02, 2015 at 10:51:03PM +0900, Oleg Endo wrote: > On Thu, 2015-10-01 at 21:30 -0400, Rich Felker wrote: > > > If you have any other general comments on the patch in the mean time > > I'd be happy to hear them. > > Below are some comments. Might be a bit unstructured, I was hopping >

Re: [PATCH] Improve DOM's optimization of control statements

On 10/02/2015 05:15 AM, Renlin Li wrote: Hi Jeff, Your patch causes an ICE regression. The test case is " gcc.c-torture/compile/pr27087.c", I observed it on aarch64-none-elf target when compiling the test case with '-Os' flag. A quick check shows, the cfg has been changed, but the loop

Re: [PATCH] Add verifier for leaked SSA names

On 10/02/2015 01:37 AM, Richard Biener wrote: The following patch doesn't pass bootstrap & regtest. It did at some point though and its comment hints that fixing leaks after inlining was too interesting a problem to solve ;) Thus patch is FYI. Richard. Index: tree-ssa.c

Re: [C PATCH] Another fix for missing diagnostics (PR c/67730)

On Fri, 2 Oct 2015, Marek Polacek wrote: > This patch continues fixing up this PR, where we were failing to give > diagnostics for attached testcases, because of NULL being defined in > a system header. Probably the best we can do at this time is just to > use

[PATCH] Cleanup of IPA-CP alignment lattices

Hi, I have already proposed this patch many months ago but it got forgotten, for a number of reasons. It does not change functionality, it only cleans up the alignment lattices, which are currently a bit clumsy. I have refreshed the patch and made sure it still bootstraps and tests fine on an

Re: [PATCH, i386] Introduce switch for Skylake Server CPU.

Hello, Patch in the bottom introduces cpuid detection for Skylake CPU supporting AVX-512. Bootstrapped. Changed test pass. Is it ok for trunk? libgcc/ * libgcc/config/i386/cpuinfo.c (get_intel_cpu): Detect "skylake-avx512". gcc/testsuite/ * gcc.target/i386/builtin_target.c: Add

patch to fix PR657756

The following patch fixes https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67756 The patch was bootstrapped and tested on x86-64. Committed as rev. 228396. Index: ChangeLog === --- ChangeLog (revision 228395) +++ ChangeLog

[PATCH, obvious, AVX-512] Add missing AVX-512 features detection.

Hello, Patch in the bottom adds missing AVX-512VBMI,IFMA features to libgcc/config/i386/cpuinfo.c and, built-in expansion and test. Comitted to main trunk as obvious. gcc/ * config/i386/i386.c (processor_features): Add F_AVX512VBMI, F_AVX512IFMA. (isa_names_table): Handle

Re: Do not describe -std=c11 etc. as experimental in c.opt help text

On Fri, Oct 02, 2015 at 05:35:39PM +0200, Marek Polacek wrote: > On Thu, Oct 01, 2015 at 05:01:26PM +, Joseph Myers wrote: > > I noticed that c.opt still described -std=c11 and related options as > > experimental in the --help text. This patch fixes this. > > > > Jason, note that

Re: Do not describe -std=c11 etc. as experimental in c.opt help text

On Fri, Oct 02, 2015 at 05:35:39PM +0200, Marek Polacek wrote: > On Thu, Oct 01, 2015 at 05:01:26PM +, Joseph Myers wrote: > > I noticed that c.opt still described -std=c11 and related options as > > experimental in the --help text. This patch fixes this. > > > > Jason, note that

Re: [PATCH] SH FDPIC backend support

On Fri, 2015-10-02 at 11:18 -0400, Rich Felker wrote: > Thanks! This is very helpful. gcc style has changed a lot since the > old patch was submitted so I think it makes sense to update it to > match current practices rather than just making it work. I'll try to > focus on any functional problems

Re: [C/C++ PATCH] RFC: Implement -Wduplicated-cond (PR c/64249) (version 2)

On Fri, Oct 02, 2015 at 08:43:30AM -0700, H.J. Lu wrote: > On Fri, Oct 2, 2015 at 3:23 AM, Marek Polacek wrote: > > On Wed, Sep 30, 2015 at 12:45:35PM -0600, Jeff Law wrote: > >> On 09/30/2015 09:47 AM, Joseph Myers wrote: > >> >The C front-end changes are OK. > >> The rest

Re: [PATCH] x86 interrupt attribute

On Fri, Oct 2, 2015 at 2:51 PM, Yulia Koval wrote: > Hi, > Here is a new patch. Added HJ's changes and review changes. > > Implement x86 interrupt attribute + incoming_stack_boundary + = (crtl->parm_stack_boundary > ix86_incoming_stack_boundary + ?

Re: [PATCH] Improve DOM's optimization of control statements

On 10/02/2015 05:15 AM, Renlin Li wrote: Hi Jeff, Your patch causes an ICE regression. The test case is " gcc.c-torture/compile/pr27087.c", I observed it on aarch64-none-elf target when compiling the test case with '-Os' flag. A quick check shows, the cfg has been changed, but the loop

Re: [patch] libstdc++/67747 Allocate space for dirent::d_name

On 02/10/15 14:41 +0200, Florian Weimer wrote: On 10/02/2015 02:34 PM, Jonathan Wakely wrote: On 02/10/15 14:16 +0200, Florian Weimer wrote: On 09/29/2015 01:37 PM, Jonathan Wakely wrote: POSIX says that dirent::d_name has an unspecified length, so calls to readdir_r must pass a buffer with

Re: [PATCH] Disable -Wduplicated-cond for the time being

On Fri, Oct 02, 2015 at 06:27:37PM +0200, Marek Polacek wrote: > Given that the new warning currently breaks bootstrap [*] and I see > no simple way how to resolve PR67819 derived out of the bootstrap > failure, I'm moving -Wduplicated-cond out of -Wall and skipping one > of the tests for the time

Re: [PATCH] Convert SPARC to LRA

On 09/30/2015 10:15 AM, Segher Boessenkool wrote: On Wed, Sep 30, 2015 at 09:15:17AM -0600, Jeff Law wrote: I guess the support of cc0 can be implemented for reasonable amount of time. It is just a priority issue. I still have a lot PRs for the targets already using LRA. I wouldn't suggest

Re: [PATCH] x86 interrupt attribute

Fixed it. Thanks. On Fri, Oct 2, 2015 at 6:45 PM, Uros Bizjak wrote: > On Fri, Oct 2, 2015 at 2:51 PM, Yulia Koval wrote: >> Hi, >> Here is a new patch. Added HJ's changes and review changes. >> >> Implement x86 interrupt attribute > > +

Re: [patch] libstdc++/67747 Allocate space for dirent::d_name

On 10/02/2015 07:37 PM, Martin Sebor wrote: > I'm not sure what you are basing this assertion on. In the man > pages I have looked at, memcpy is documented as MT-Safe. readdir > is documented as MT-Unsafe. The Unsafe definition is clear: > contains global and static data that is not protected. I

Re: [Patch, fortran] PR67721 deep copy missing when assigning derived type constructor to an array

On Fri, Oct 02, 2015 at 09:33:33AM -0700, H.J. Lu wrote: > On Sat, Sep 26, 2015 at 6:10 AM, Mikael Morin wrote: > > Hello, > > > > I've just submitted this PR, and the patch as well, which passes the > > testsuite. > > > > The problem is a missing deep copy when the rhs is a

Re: [Patch AArch64] Use default_elf_asm_named_section instead of special cased hook

On 2 October 2015 at 15:05, Marcus Shawcroft wrote: > On 2 October 2015 at 14:01, Ramana Radhakrishnan > wrote: > #undef TARGET_ASM_NAMED_SECTION -#define TARGET_ASM_NAMED_SECTION aarch64_elf_asm_named_section

Re: [PATCH] Introduce ROUND_UP and ROUND_DOWN macros

On 10/02/2015 06:42 PM, Uros Bizjak wrote: Attached patch introduces ROUND_UP and ROUND_DOWN global macros. These come handy to round and align various values, as shown by the usage in config/i386/ files. * system.h (ROUND_UP): New macro definition. (ROUND_DOWN): Ditto. *

Re: [patch] libstdc++/67747 Allocate space for dirent::d_name

On 10/02/2015 07:53 PM, Martin Sebor wrote: > Here's the older page: > http://docs.oracle.com/cd/E19683-01/816-0213/6m6ne3895/index.html > > With that, I agree that using readdir is thread-safe on Solaris 11.2. > It is not safe on Solaris 9, and it would not be safe on other systems > that don't

RFC: PATCH for front end parts of C++ transactional memory TS

This patch implements the front end bits of the transactional memory technical specification: apart from parsing, that means treating transaction_safe as part of the type and dealing with conversions, mangling and such. Since the transaction_safe attribute now affects type identity, I needed

[PATCH] Introduce ROUND_UP and ROUND_DOWN macros

Hello! Attached patch introduces ROUND_UP and ROUND_DOWN global macros. These come handy to round and align various values, as shown by the usage in config/i386/ files. In addition to target independent code, many targets could benefit from these universal macros (e.g. arm and aarch64 can

Re: [Patch AArch64] Use default_elf_asm_named_section instead of special cased hook

On Fri, Oct 2, 2015 at 5:40 PM, Christophe Lyon wrote: > On 2 October 2015 at 15:05, Marcus Shawcroft > wrote: >> On 2 October 2015 at 14:01, Ramana Radhakrishnan >> wrote: >> > #undef

Re: C PATCH for c/65345 (file-scope _Atomic expansion with floats)

On 01/10/15 17:18, Marek Polacek wrote: > On Thu, Oct 01, 2015 at 11:02:09AM -0400, David Edelsohn wrote: >> On Thu, Oct 1, 2015 at 10:49 AM, Marek Polacek wrote: >>> Joseph reminded me that I had forgotten about this patch. As mentioned >>> here

Re: [patch] libstdc++/67747 Allocate space for dirent::d_name

On 10/02/2015 11:09 AM, Florian Weimer wrote: On 10/02/2015 06:57 PM, Martin Sebor wrote: Readdir isn't required to be thread-safe (it may reference global data) so calling it in multiple threads even with a different dirp argument is undefined. A thread-unsafe implementation can meet the

Re: Do not use TYPE_CANONICAL in useless_type_conversion

> > On Fri, 2 Oct 2015, Jan Hubicka wrote: > > > > > > There must be a reason why I allowed modes to differ there btw ;) > > > > > > Thinking about it, I guess reason is that incomplete types do not have > > > resonable modes set, so requiring modes to match will prevent complete > > > and

Re: [patch] libstdc++/67747 Allocate space for dirent::d_name

On 10/02/2015 06:57 PM, Martin Sebor wrote: > Readdir isn't required to be thread-safe (it may reference global > data) so calling it in multiple threads even with a different dirp > argument is undefined. A thread-unsafe implementation can meet the > POSIX requirement and still access global

  1   2   >