* Bernd Schmidt [2016-11-03 13:01:32 +0100]:
> On 09/14/2016 03:00 PM, Andrew Burgess wrote:
> > In an attempt to get this patch merged (as I still think that its
> > correct) I've investigated, and documented a little more about how I
> > think things currently work. I'm
On November 16, 2016 7:22:51 PM GMT+01:00, Jakub Jelinek
wrote:
>Hi!
>
>As mentioned in the PR, libcpp uses gcc_assert in a couple of places,
>but guards it with ENABLE_ASSERT_CHECKING macro that is never defined
>in libcpp.
>
>This patch arranges for it to be defined if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78299
Jakub Jelinek changed:
What|Removed |Added
Summary|[6/7 Regression] ICE in |[6 Regression] ICE in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61409
--- Comment #24 from Jeffrey A. Law ---
OK. It's coming back to me now. And yes, Aldy, it was the edge 9->6 :-)
So we have a PHI argument that references an uninitialized variable. There is
a control predicate for that PHI argument, call it
Ping^2. Link to original post:
https://gcc.gnu.org/ml/gcc-patches/2016-10/msg02305.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69298
--- Comment #6 from janus at gcc dot gnu.org ---
Here is a further reduced test case, based on Dominique's variant in comment
#2, which (I think) runs into the same runtime-segfault when calling
stuff_1d_finaliser ...
module stuff_mod
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78385
Bug ID: 78385
Summary: Build of libgcc2 for target arm-eabi fails, if
configuration --with-abi=apcs-gnu is used (in
GCC-Build)
Product: gcc
Version: 6.2.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78351
--- Comment #16 from Steve Kargl ---
On Wed, Nov 16, 2016 at 06:36:58PM +, kevin.b.beard at nasa dot gov wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78351
>
> --- Comment #13 from Dr. Kevin B. Beard ---
> Hi,
>
> Thanks for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78351
--- Comment #15 from Jerry DeLisle ---
Well, on further investigation I see that we do have a flag in read_sf to
signal a comma. It does not have this flag in read_sf_internal, So definitely
does not work on strings. My bet is that when we/I
On Wed, 16 Nov 2016, Mike Stump wrote:
Looks reasonable. The biggest issue would be if any of those values
changed through time, and the current version works for older netbsd
releases, the patch could break them. Of course, I don't have any
visibility into how any of those values might
This patch adds a test to the cmpstrnsi pattern in i386.md so that it
will bail out (FAIL) if neither of the strings is a constant string. It
can only work as a proper strncmp if the length is not longer than both
of the strings. This change is required if expand_builtin_strncmp is
going to try
This patch makes expand_builtin_strncmp attempt to expand via cmpstrnsi
even if neither of the string arguments are string constants.
2016-11-16 Aaron Sawdey
* builtins.c (expand_builtin_strncmp): Attempt expansion of strncmp
via cmpstrnsi even if
Builtin expansion of strncmp currently only happens when at least one
of the string arguments is a constant string. Two pieces are needed to
enable this:
1) Fix i386.md cmpstrnsi pattern. It uses repzcmpsb which does not
actually test for the zero byte ending the string. So this is only a
valid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78374
Markus Eisenmann changed:
What|Removed |Added
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78384
Bug ID: 78384
Summary: [7 Regression] ICE: verify_flow_info failed (error:
wrong outgoing edge flags at end of bb 15)
Product: gcc
Version: 7.0
Status: UNCONFIRMED
> On Nov 16, 2016, at 9:12 AM, Krister Walfridsson
> wrote:
>
> NetBSD fails bootstrap with
> stdatomic.h:55:17: error: unknown type name '__INT_LEAST8_TYPE__'
> This is fixed by the following patch (only i386 and x86_64 for now. I'll
> do the other ports after
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78351
--- Comment #14 from Dominique d'Humieres ---
Try to find what you want in http://www.fortran.com/F77_std/rjcnf0001.html.
Good luck!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78378
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61409
--- Comment #23 from Jeffrey A. Law ---
Sorry, I can't remember if I meant 9->5 or 9->6 at this point :-) I need to
refamiliarize myself with this stuff again to make sure I've got the basic
concepts before reviewing the patch.
But you can
On Nov 16, 2016, at 10:58 AM, Mike Stump wrote:
>
> Yeah, I easily could have approved it as well, so no worries.
Oh. I see I did approve the original patch, sorry for not catching it. Thanks
for all your work.
On Nov 16, 2016, at 7:57 AM, Tamar Christina wrote:
>
> Forgot to include the committed patch.
>>> This is causing all test names to depend on $srcdir. A test name
>>> should never include the value of $srcdir.
>>
>> Sorry about that, committed a fix as r242500 under
On Thu, Nov 17, 2016 at 12:19:37AM +0530, Prathamesh Kulkarni wrote:
> --- a/gcc/tree-vrp.c
> +++ b/gcc/tree-vrp.c
> @@ -1069,6 +1069,34 @@ gimple_assign_nonzero_warnv_p (gimple *stmt, bool
> *strict_overflow_p)
> }
> }
>
> +/* Return true if STMT is known to contain call to a
On 11/16/2016 11:34 AM, Jeff Law wrote:
On 10/26/2016 10:37 AM, Martin Sebor wrote:
When formatting an integer constant using the %E directive GCC
includes a suffix that indicates its type. This can perhaps be
useful in some situations but in my experience it's distracting
and gets in the way
On 11/01/2016 10:27 AM, Segher Boessenkool wrote:
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
Hi Richard,
Following your suggestion in PR78154, the patch checks if stmt
contains call to memmove (and friends) in gimple_stmt_nonzero_warnv_p
and returns true in that case.
Bootstrapped+tested on x86_64-unknown-linux-gnu.
Cross-testing on arm*-*-*, aarch64*-*-* in progress.
Would it be OK to
On 10/28/2016 05:51 AM, Richard Biener wrote:
These are the middle-end changes and additions to the testsuite.
They are pretty self-contained, I've organized the changelog
entries below in areas of changes:
1) dump changes - we add a -gimple dump modifier that allows most
function dumps to
> -Original Message-
> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-
> ow...@gcc.gnu.org] On Behalf Of Jakub Jelinek
> Sent: Thursday, November 10, 2016 7:53 AM
> To: Jason Merrill
> Cc: gcc-patches List
> Subject: Re: RFA: PATCH to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78351
--- Comment #13 from Dr. Kevin B. Beard ---
Hi,
Thanks for looking at this. I'm sorry to say I don't have access to the
official F77 standards,
perhaps you could send me a copy of the whole? The section you quoted doesn't
seems to
to exclude
This patch to libgo replaces runtime/runtime1.goc with Go and C code.
This is a step toward eliminating goc2c.
This drops the exported parfor code; it was needed for tests in the
past, but no longer is. The Go 1.7 runtime no longer uses parfor.
Bootstrapped and ran Go testsuite on
On 10/26/2016 10:37 AM, Martin Sebor wrote:
When formatting an integer constant using the %E directive GCC
includes a suffix that indicates its type. This can perhaps be
useful in some situations but in my experience it's distracting
and gets in the way when writing tests.
Here's an example:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78324
David Malcolm changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
On 10/14/2016 12:28 PM, Bernd Schmidt wrote:
On 10/12/2016 09:27 PM, Denys Vlasenko wrote:
Yes, something like "if max_skip >= func_size, temporarily lower
max_skip to func_size-1" (because otherwise we can create padding
bigger-or-equal to the entire function in size, which is stupid
- it's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50217
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
Hi!
As mentioned in the PR, libcpp uses gcc_assert in a couple of places,
but guards it with ENABLE_ASSERT_CHECKING macro that is never defined
in libcpp.
This patch arranges for it to be defined if ENABLE_ASSERT_CHECKING
is going to be defined in gcc subdir.
Bootstrapped/regtested on
Hi!
When broken_loop is true (i.e. the OMP_FOR body doesn't return),
loop->header doesn't have to be equal to body_bb, but it makes no sense to
verify it. We aren't adding any loop in that case anyway.
Bootstrapped/regtested on x86_64-linux and i686-linux, committed to trunk.
2016-11-16 Jakub
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78299
--- Comment #3 from Jakub Jelinek ---
Author: jakub
Date: Wed Nov 16 18:19:09 2016
New Revision: 242507
URL: https://gcc.gnu.org/viewcvs?rev=242507=gcc=rev
Log:
PR fortran/78299
* omp-low.c (expand_omp_for_static_nochunk): Don't
Hi,
I've rebased the patch to make arm_feature_set agree with type of FL_* macros on
top of trunk rather than on top of the optional -mthumb patch. That involved
doing the changes to gcc/config/arm/arm-protos.h rather than
gcc/config/arm/arm-flags.h. I also took advantage of the fact that
2016-11-16 19:21 GMT+03:00 Bernd Schmidt :
> On 11/15/2016 05:31 PM, Andrew Senkevich wrote:
>>
>> 2016-11-15 17:56 GMT+03:00 Jeff Law :
>>>
>>> On 11/15/2016 05:55 AM, Andrew Senkevich wrote:
2016-11-11 14:16 GMT+03:00 Uros Bizjak
[ I'm catching up on a variety of things... So apologies if y'all
have settled these issues. ]
On 11/02/2016 01:32 PM, Jakub Jelinek wrote:
But obviously not all levels of the warning can/should be enabled
with -Wall/-Werror. There are cases which are worth warning by default
(the case
On 11/16/2016 06:12 PM, Krister Walfridsson wrote:
I'm the NetBSD maintainer, so I belive I don't need approval to commit
this. But I have been absent for a long time, so it makes sense for
someone to review at least this first patch.
Bootstrapped and tested on i386-unknown-netbsdelf6.1 and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51119
--- Comment #46 from Thomas Koenig ---
(In reply to Jerry DeLisle from comment #44)
> Yes I am aware of these. I was willing to live with them, but if it is a
> problem, we can remove those options easy enough.
I think it is no big deal, but
On Fri, Nov 11, 2016 at 1:33 PM, Jiong Wang wrote:
> The encoding for new added AARCH64 DWARF operations.
This patch seems rather incomplete; I only see a change to
dwarf2out.c, which won't compile since the opcodes aren't defined
anywhere.
Jason
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78378
--- Comment #5 from Jakub Jelinek ---
Scratch that, I've missed there the 8 SUBREG_BYTE. That one is fine.
What is wrong is combine_simplify_rtx turning
(set (reg:SI 99 [ x ])
(and:SI (subreg:SI (truncate:HI (lshiftrt:TI (mult:TI
On 11/16/2016 09:44 AM, Richard Sandiford wrote:
This may no longer be necessary with the current version
of the SVE patches, but it does at least make things consistent
with the TYPE_MODE/SET_TYPE_MODE split.
Tested on aarch64-linux-gnu and x86_64-linux-gnu. OK to install?
Thanks,
Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41539
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.7.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44131
janus at gcc dot gnu.org changed:
What|Removed |Added
CC||janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44863
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.6.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44864
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.6.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45795
janus at gcc dot gnu.org changed:
What|Removed |Added
CC||janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49961
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.6.0
On November 16, 2016 5:22:17 PM GMT+01:00, Marc Glisse
wrote:
>On Wed, 16 Nov 2016, Michael Matz wrote:
>
>> Hi,
>>
>> On Wed, 16 Nov 2016, Marc Glisse wrote:
>>
> The first sentence about ORing the sign bit sounds strange (except
>for a
> sign-magnitude
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51791
janus at gcc dot gnu.org changed:
What|Removed |Added
CC||janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51207
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.7.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51943
janus at gcc dot gnu.org changed:
What|Removed |Added
CC||janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55935
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.8.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56929
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56845
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57145
janus at gcc dot gnu.org changed:
What|Removed |Added
CC||janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57456
janus at gcc dot gnu.org changed:
What|Removed |Added
CC||janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57922
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78383
Bug ID: 78383
Summary: label as values ICE with C++ lambda
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58947
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.8.1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58658
janus at gcc dot gnu.org changed:
What|Removed |Added
CC||janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60834
janus at gcc dot gnu.org changed:
What|Removed |Added
CC||janus at gcc dot gnu.org
I'm looking for a review of the patch below:
https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00779.html
Thanks
On 11/08/2016 05:09 PM, Martin Sebor wrote:
The -Wformat-length checker relies on the compute_builtin_object_size
function to determine the size of the buffer it checks for overflow.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60255
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.9.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60322
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |6.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60550
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.9.1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63553
janus at gcc dot gnu.org changed:
What|Removed |Added
CC||janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78314
nsz at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |7.0
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64589
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |6.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64674
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |6.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67091
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |6.0
Hi,
I'd like to ping for these two patches:
[PATCH, ARM] Further improve stack usage on sha512 (PR 77308)
https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00523.html
[PATCH, ARM] Enable ldrd/strd peephole rules unconditionally
https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00830.html
Thanks
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78314
--- Comment #3 from nsz at gcc dot gnu.org ---
Author: nsz
Date: Wed Nov 16 17:27:04 2016
New Revision: 242505
URL: https://gcc.gnu.org/viewcvs?rev=242505=gcc=rev
Log:
[PR libgfortran/78314] Fix ieee_support_halting
ieee_support_halting only
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64209
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |5.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60359
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59547
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55855
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.8.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49962
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.5.4
Hi,
Currently test gfortran.dg/vect/fast-math-mgrid-resid.f checks all predictive
commoning opportunities for all possible loops. This makes it fragile because
vectorizer may peel the loop differently, as well as may choose different
vector factors. For example, on x86-solaris, vectorizer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46662
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.6.0
Attached is an updated version of the patch that also adds attribute
alloc_size to the standard allocation built-ins (aligned_alloc,
alloca, malloc, calloc, and realloc) and handles alloca.
Besides that, I've renamed the option to -Walloc-size-larger-than
to make it less similar to
Hi,
Dump information of IVOPT has been updated while test string
gcc.target/arm/ivopts-orig_biv-inc.c is not. This patch does this. Test
result checked on arm-none-eabi. Commit as obvious?
Thanks,
bin
gcc/testsuite/ChangeLog
2016-11-16 Bin Cheng
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69011
janus at gcc dot gnu.org changed:
What|Removed |Added
CC||janus at gcc dot gnu.org
> gcc/testsuite/
> 2016-11-16 Szabolcs Nagy
>
> PR libgfortran/78314
> * gfortran.dg/ieee/ieee_6.f90: Use ieee_support_halting.
>
> libgfortran/
> 2016-11-16 Szabolcs Nagy
>
> PR libgfortran/78314
> * config/fpu-glibc.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60234
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59941
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.7.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58436
janus at gcc dot gnu.org changed:
What|Removed |Added
CC||janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56385
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.6.4
On Tue, 15 Nov 2016, Matthew Fortune wrote:
> I'm a little concerned the expected output tests may be fragile over
> time but let's wait and see.
Indeed, but I'd rather see false negatives than false positives or no
coverage at all. And I hope the pieces of expected assembly quoted will
help
NetBSD fails bootstrap with
stdatomic.h:55:17: error: unknown type name '__INT_LEAST8_TYPE__'
This is fixed by the following patch (only i386 and x86_64 for now. I'll
do the other ports after fixing some more issues -- the NetBSD support is
rather broken at the moment...)
I'm the NetBSD
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52531
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.8.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55905
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.9.3
On 11/14/2016 01:34 PM, Eric Gallager wrote:
On 11/13/16, Martin Sebor wrote:
Bug 77531 requests a new warning for calls to allocation functions
(those declared with attribute alloc_size(X, Y)) that overflow the
computation X * Z of the size of the allocated object.
Bug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78382
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
On Wed, Nov 16, 2016 at 04:15:10PM +, Andrew Stubbs wrote:
> On 16/11/16 13:10, Michael Meissner wrote:
> >Yeah, SFmode and DFmode should not have the TARGET_{S,D}F_FPR checks.
>
> So, I can safely resolve my initial problem by simply removing them?
> And that wouldn't break the other use of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54756
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |5.0
On 11/16/2016 05:52 PM, Richard Sandiford wrote:
Using rtx_mode_t also abstracts away the representation. The fact that
it's a std::pair rather than a custom class isn't important to users of
the interface.
Looks borderline obvious to me. OK.
Bernd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51947
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.9.0
101 - 200 of 599 matches
Mail list logo