[patch, fortran] Fix PR 67219, erroneous warning

2016-10-30 Thread Thomas Koenig
Hello world, the regression in question was caused by issuing a conversion warning for a complex constant too early, when the statement would be rejected later. The solution is to throw away the warning if we do not find that comma. Regression-tested. OK for trunk and 6-branch? Regards

libgo patch committed: Use GNU make to eliminate duplication in Makefile.am

2016-10-30 Thread Ian Lance Taylor
This patch to libgo uses GNU make features to eliminate a lot of duplication in libgo/Makefile.am. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline. The attached patch, generated by `svn diff`, doesn't seem to correctly reflect the fact that libgo/runtime/runtime.c

Go patch committed: Fix slice/array evaluation order bug

2016-10-30 Thread Ian Lance Taylor
This patch to the Go frontend by Than McIntosh fixes an order-of-evaluation bug in slice/array composite literals. There was a phase ordering issue in the handling of "keyed" array literal expressions: the lowering phase was canonicalizing the indices/vals before the phase that fixed evaluation or

Re: [patch, fortran] Fix PR 67219, erroneous warning

2016-10-30 Thread Steve Kargl
On Sun, Oct 30, 2016 at 05:32:52PM +0100, Thomas Koenig wrote: > > the regression in question was caused by issuing a conversion > warning for a complex constant too early, when the statement would be > rejected later. > > The solution is to throw away the warning if we do not find that > comma.

[C++ PATCH] Add tests for a const member and a reference member for launder.

2016-10-30 Thread Ville Voutilainen
So, how about adding these? They should give us regression tests that make sure launder does the right in in case some optimizations attempt to reuse const/reference members. Tested on Linux-x64. 2016-10-30 Ville Voutilainen Add tests for a const member and a reference member for launder.

[PATCH] bb-reorder: Improve compgotos pass (PR71785)

2016-10-30 Thread Segher Boessenkool
For code like the testcase in PR71785 GCC factors all the indirect branches to a single dispatcher that then everything jumps to. This is because having many indirect branches with each many jump targets does not scale in large parts of the compiler. Very late in the pass pipeline (right before p

Re: [PATCH] DWARF5 .debug_info headers, .debug_types -> .debug_info DW_UT_type

2016-10-30 Thread Jan Kratochvil
On Fri, 21 Oct 2016 21:32:42 +0200, Jakub Jelinek wrote: > This patch changes the .debug_info headers to follow the current > specification (I still hope the useless padding1/padding2 fields will be > removed), and also changes the -gsplit-dwarf stuff to move dwo_id into > the header and use DW_UT_

Re: [PATCH] Add -Wshadow-local and -Wshadow-compatible-local.

2016-10-30 Thread Mark Wielaard
On Tue, Oct 25, 2016 at 01:57:09AM +0200, Mark Wielaard wrote: > I think the only thing "blocking" the patch from going in is that > nobody made a decission on how the actual warning option should be > named. I think the suggestion for -Wshadow=[global|local|compatible-local] > is the right one. Wi

[patch, libgfortran] Bug 78123 - Short reads with T edit descriptor not padding correctly

2016-10-30 Thread Jerry DeLisle
See patch below which is very simple. We were handling the case where we tabbed left of current position in the record by clearing the seen_eor flag. We were not handling the case where we tab toward the right and so are still at eor. New test case attached. Regression tested on x86-64-linux.

Re: [patch, libgfortran] Bug 78123 - Short reads with T edit descriptor not padding correctly

2016-10-30 Thread Steve Kargl
On Sun, Oct 30, 2016 at 01:21:41PM -0700, Jerry DeLisle wrote: > See patch below which is very simple. We were handling the case > where we tabbed left of current position in the record by clearing > the seen_eor flag. We were not handling the case where we tab > toward the right and so are still a

Re: [patch, libgfortran] Bug 78123 - Short reads with T edit descriptor not padding correctly

2016-10-30 Thread Thomas Koenig
Hi Jerry, See patch below which is very simple. We were handling the case where we tabbed left of current position in the record by clearing the seen_eor flag. We were not handling the case where we tab toward the right and so are still at eor. New test case attached. Regression tested on x86-6

Re: [PATCH] enhance buffer overflow warnings (and c/53562)

2016-10-30 Thread Martin Sebor
Attached is an updated patch that adds checks for excessive sizes and bounds (those in excess of SIZE_MAX / 2), and also enables the same checking for strcat and strncat). This version also fixes an issue with the interpretation of anti-ranges in the first patch. The improvements exposed two bug

Re: relax rule for flexible array members in 6.x (78039 - fails to compile glibc tests)

2016-10-30 Thread Martin Sebor
Thanks Jeff. I'll take care of the nits before I commit the patch and update the Web page this week. Jason, assuming you agree that the checking should be relaxed for 6.0, can you please let me know if it's good to commit? Martin On 10/24/2016 09:13 AM, Jeff Law wrote: On 10/21/2016 05:47 PM,

Re: [PATCH] Fix host_size_t_cst_p predicate

2016-10-30 Thread Richard Sandiford
Richard Biener writes: > On Thu, Oct 27, 2016 at 5:06 PM, Martin Liška wrote: >> On 10/27/2016 03:35 PM, Richard Biener wrote: >>> On Thu, Oct 27, 2016 at 9:41 AM, Martin Liška wrote: Running simple test-case w/o the proper header file causes ICE: strncmp ("a", "b", -1); 0xe7