https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79940
--- Comment #3 from Jakub Jelinek ---
I'll fix this, that said the testcase certainly is not OpenMP compliant, you
have a data race in there, you need to do the taskloop just once, or make sure
that in each thread it will write to different
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79484
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79867
--- Comment #1 from Daniel Santos ---
Minor correction: LD_LIBRARY_PATH is used to resolve lib names when dlopen() is
called, but not for load-time linking.
There are also a few other complications on Cygwin. DLLs (including libgcc)
are stored
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79671
Jakub Jelinek changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78939
--- Comment #7 from Jakub Jelinek ---
Has there been any resolution for the GB20 vs. LWG2446 conflict in Kona?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79955
Bug ID: 79955
Summary: GLIBC build fails after r245840
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79484
--- Comment #4 from smateo ---
Hi Jerry,
This code is a simplification of a code that our tool generates to support a
tasking programming model. I know that I don't need a derived type to call a C
function. If I recall correctly, I needed to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70549
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79945
Pavel Zhukov changed:
What|Removed |Added
CC||pavel at zhukoff dot net
--- Comment #5
On Fri, Mar 3, 2017 at 6:46 AM, Sam Thursfield
wrote:
>
> I hit this compile warning running `make check` on AIX. Since -Werror is
> enabled by default here it causes a build failure.
>
> Tested on powerpc-ibm-aix7.2.0.0
>
> This my first patch submission for GCC,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79928
Chung-Ju Wu changed:
What|Removed |Added
CC||jasonwucj at gcc dot gnu.org
--- Comment
Martin Sebor on 2017/3/8 08:09 wrote:
The following one-line patch corrects the spelling of the error
message in the nds32 back end pointed out by a translator. I'll
go ahead and commit it as trivial unless there are objections in
the next day or so.
Martin
2017-03-07 Martin Sebor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78939
Jonathan Wakely changed:
What|Removed |Added
Keywords||rejects-valid
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79928
Martin Sebor changed:
What|Removed |Added
Keywords||patch
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79936
Martin Sebor changed:
What|Removed |Added
Keywords|diagnostic |patch
--- Comment #7 from Martin Sebor
In bug 79936 - ICE with -Walloc-size-larger-than=32767 the reporter
encountered an ICE on x86_64-apple-darwin10.8.0 caused by GCC source
file that implements the warning accessing a global tree without
having included the file in GTFILES make variable. (Thanks again
to David Malcolm who helped
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79948
Martin Sebor changed:
What|Removed |Added
Keywords||rejects-valid
The following one-line patch corrects the spelling of the error
message in the nds32 back end pointed out by a translator. I'll
go ahead and commit it as trivial unless there are objections in
the next day or so.
Martin
2017-03-07 Martin Sebor
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79948
--- Comment #1 from Andrew Pinski ---
I have not read the standard in this area but I know somethings are interesting
in this area that most folks won't expect. Inside #if undefined macros are
considered as 0.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79928
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
Don't let pointer randomization change the order in which we process
store chains. This may cause SSA_NAMEs to be released in different
order, and if they're reused later, they may cause differences in SSA
partitioning, leading to differences in expand, and ultimately to
different code.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71543
Martin Sebor changed:
What|Removed |Added
Keywords||ice-on-invalid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79952
--- Comment #1 from Martin Sebor ---
Removing --enable-checking=all from the set of configure options or replacing
it with --enable-checking=release allows the build to complete.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79954
Bug ID: 79954
Summary: [C++17] Explicit deduction guide not rejected when
defined outside inline namespace enclosing the type
Product: gcc
Version: 7.0.1
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79501
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79942
Martin Sebor changed:
What|Removed |Added
Keywords||documentation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79953
Bug ID: 79953
Summary: ICE in expand_debug_locations when attribute target is
used
Product: gcc
Version: 6.3.0
Status: UNCONFIRMED
Severity: normal
On Tue, 2017-03-07 at 22:52 +0100, Jakub Jelinek wrote:
> On Tue, Mar 07, 2017 at 03:36:38PM -0600, Will Schmidt wrote:
> > Per PR79941, we are folding the vec_mul{e,o}* operations improperly. Those
> > entries were added to the intrinsics-to-be-folded list where the generic
> > multiplies should
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79952
Bug ID: 79952
Summary: [7 Regression] ICE in test_loading_cfg in
read-rtl-function.c:2016 targeting for
hppa2.0w-hp-hpux11.11
Product: gcc
Version: 7.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79916
--- Comment #5 from Martin Liška ---
That's strange, cc1plus command line has nothing special as I can see:
$
/home/marxin/BIG/buildbot/slave/install/gcc-dda535fd9490e3e8f31bacc6678e0c734ff59212/bin/../lib/gcc/ppc64le-linux-gnu/7.0.1/cc1plus
On 7 March 2017 13:43:00 CET, Nitish Kumar Mishra
wrote:
>Hi,
>
>I have update the patch according to some comments from GDB community.
>Please find the attachments.
If it is AIX specific, you probably should not remove fuchsia support.
And since we most likely do
Snapshot gcc-5-20170307 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20170307/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79951
Bug ID: 79951
Summary: ICE in extract_insn, at recog.c:2311 on ppc64le with
-mno-cmpb
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79936
Martin Sebor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79916
--- Comment #4 from Bernd Schmidt ---
I also have trouble reproducing this. Rather than the g++ commandline, please
post what is passed to cc1plus.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79949
--- Comment #1 from Martin Liška ---
Same happens here:
$ s390x-linux-gnu-gcc
/home/marxin/Programming/gcc/gcc/testsuite/c-c++-common/torture/builtin-arith-overflow-p-19.c
-O2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79916
--- Comment #3 from Martin Liška ---
Btw. GCC 5 and GCC 6 work fine.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79950
Bug ID: 79950
Summary: G++ cannot detect simple off by one error in STL
classes
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79949
Bug ID: 79949
Summary: ICE in Max. number of generated reload insns per insn
is achieved (90)
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Keywords: ra
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79916
--- Comment #2 from Martin Liška ---
There's how I created the cross-compiler:
$ configure --target=ppc64le-linux-gnu
--with-as=/usr/bin/powerpc64le-suse-linux-as --disable-bootstrap
$ ppc64le-linux-gnu-g++ -v
...
gcc version 7.0.1 20170307
On Tue, Mar 07, 2017 at 03:36:38PM -0600, Will Schmidt wrote:
> Per PR79941, we are folding the vec_mul{e,o}* operations improperly. Those
> entries were added to the intrinsics-to-be-folded list where the generic
> multiplies should have been instead. Test coverage in place was for the
> generic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64236
--- Comment #5 from John Paul Adrian Glaubitz ---
Still reproducible on gcc-7 (r243972).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79484
--- Comment #3 from Jerry DeLisle ---
Using LOC is not the right way to do these things. You should use bind(c) on
the fortran side.
I think you can google help with this.
Power8 systems are less forgiving then others. I dont get any errors on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79936
--- Comment #5 from Martin Sebor ---
After spending some more time debugging this I don't think it's a bug in the
warning after all. The ICE comes and goes with different arguments to
-Walloc-size-larger-than. It's as if the block the pointer
Hi,
Per PR79941, we are folding the vec_mul{e,o}* operations improperly. Those
entries were added to the intrinsics-to-be-folded list where the generic
multiplies should have been instead. Test coverage in place was for the
generic multiplies, and this was missed by my testing.
Thusly, remove
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79948
Bug ID: 79948
Summary: _Pragma(“GCC error”) is processed differently inside
and outside of a #if directive
Product: gcc
Version: 5.4.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79946
--- Comment #2 from Adam Hirst ---
Just for clarification: is this only occuring for the case where one does
Dx = D%x
tmp = matmul(NU,Dx);
tensorproduct%x = dot_product(tmp,NV)
or is it also applicable to
tmp =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79671
Jonathan Wakely changed:
What|Removed |Added
Resolution|INVALID |FIXED
--- Comment #30 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79936
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79484
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79899
--- Comment #2 from Martin Liška ---
Same happens on ppc64-linux-gnu target:
$ ppc64-linux-gnu-g++
/home/marxin/Programming/gcc/gcc/testsuite/g++.dg/other/friend5.C -Os
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79947
Bug ID: 79947
Summary: [6/7 Regression] ICE in rs6000_emit_swsqrt at
gcc/config/rs6000/rs6000.c:37570
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Keywords:
Hi,
in the diagnostics the %qs specifier is used in most of the cases. But
there are some cases left where the more complicated %<%s%> is used. Is
there a good reason to prefer the complicated spelling?
Same for %<%T%> and %qT, and similar letters.
Regards,
Roland
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79912
Andrew Waterman changed:
What|Removed |Added
CC||andrew at sifive dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79944
--- Comment #4 from Dmitry Vyukov ---
Attached second minimized reproducer.
Build it with:
gcc dmaengine2.c -fsanitize=address -O2 -lasan -g
It produces:
==57662==ERROR: AddressSanitizer: unknown-crash on address 0x00601321 at pc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79944
--- Comment #3 from Dmitry Vyukov ---
Created attachment 40918
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40918=edit
reproducer2
On Tue, 7 Mar 2017, Jeff Law wrote:
>> When/if this has been accepted, is it okay to pull the latest config.guess
>> into GCC even at this stage of the release process? (We're only looking
>> at this change and the addition of nsx-tandem compared to what we have
>> right now.)
> If it's just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79834
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79912
mpf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|mpf at gcc dot gnu.org |palmer at dabbelt dot
Hi!
The Fortran FE registers its own format decoder, overriding the default
one that handles what the middle-end can emit, e.g.
warning (OPT_Wpadded, "padding struct to align %q+D", field);
The C/C++ FEs are the only other ones that override the decoder, but they
do handle all the specs the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79896
Marek Polacek changed:
What|Removed |Added
CC||gerhard.steinmetz.fortran@t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79776
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79785
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79912
Palmer Dabbelt changed:
What|Removed |Added
CC||palmer at dabbelt dot com
--- Comment
Hi!
This patch should make life easier for the translators by emitting
just one translatable message about pragmas only allowed in compound
statements, instead of 13 different ones. In addition to that
it stops using c*_parser_error for that, both so that the msgid
can use %s and to avoid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79834
--- Comment #2 from Jakub Jelinek ---
Author: jakub
Date: Tue Mar 7 19:07:44 2017
New Revision: 245959
URL: https://gcc.gnu.org/viewcvs?rev=245959=gcc=rev
Log:
PR c/79834
c/
* c-parser.c (c_parser_pragma): Use error_at instead
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79946
--- Comment #1 from Thomas Koenig ---
Created attachment 40917
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40917=edit
Assembly output for ifort
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79946
Bug ID: 79946
Summary: Suboptimal code with AVX2 copying all arguments to
stack
Product: gcc
Version: 7.0.1
Status: UNCONFIRMED
Severity: enhancement
Hi!
Apparently in error recovery, populate_clone_array can't return fns
with all NULLs. maybe_thunk_body used to handle that fine, but
the newly added ctor_omit_inherited_parms call ICEs.
Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux, ok for
trunk?
2017-03-07 Jakub
Hi!
Doing copy_node on error_mark_node doesn't work too well, lots of spots
in the compiler assume there is just a single error_mark_node and compare
it using pointer comparison, rather than checking for TREE_CODE () ==
ERROR_MARK. The testcase ICEs in particular during gimplification,
the
Hi!
If any of the operands of the UBSAN_{ADD,SUB,MUL}_OVERFLOW ifn with
vector operand is a uniform vector, expanding it as VCE on the VECTOR_CST
followed by ARRAY_REF with variable index in the loop is unnecessarily
expensive and nothing fixes it afterwards.
This works around ICE on s390 at
Hi!
I've preprocessed x86intrin.h with -O0 and -O2, both with -E -dD,
and gathered all _mm starting inline function names at column zero
and #define _mm macro names and compared them.
This revealed that 64 intrinsics have similar bug in avx512vlintrin.h,
no other problems found.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72783
--- Comment #5 from Martin Sebor ---
(In reply to felix from comment #4)
>
> By the way: in my report, I suggested making -Wformat-security enable this
> warning. Will -Wformat-length be implied by -Wformat-security?
I think the role of
Hi!
As mentioned in the PR, 6 intrinsics were only defined in section
guarded with #ifdef __OPTIMIZE__ (unnecessarily, because the intrinsics
don't have any immediate argument that must be constant) and without
#defines for -O0.
Fixed thusly, bootstrapped/regtested on x86_64-linux and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79816
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79930
--- Comment #10 from Thomas Koenig ---
(In reply to Richard Biener from comment #9)
> If dot_product (matmul (...), ..) can be implemented more optimally (is
> there a blas/lapack primitive for it?) then the best course of action is to
> pattern
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79945
Eric Botcazou changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79945
--- Comment #3 from Eric Botcazou ---
It's already present in system.ads so it should.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79945
--- Comment #2 from Jakub Jelinek ---
If it works, even better.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79944
--- Comment #2 from Dmitry Vyukov ---
I've shutup that bug with dest = NULL, but then I immediately got this:
BUG: KASAN: global-out-of-bounds in clear_bit
include/linux/bitops_compiler.h:15 [inline]
BUG: KASAN: global-out-of-bounds in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79945
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79945
Bug ID: 79945
Summary: ppc64le Default_Bit_Order in Ada
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79912
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79944
--- Comment #1 from Jakub Jelinek ---
I'll have a look tomorrow.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79785
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
On 03/01/2017 07:03 AM, Richard Biener wrote:
The following addresses a regression in uninit warnings that happens
because clobber stmts preclude the very simple-minded support we have
for memory. The patch fixes this by instead implementing uninit
warnings for memory properly, using the alias
40915
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40915=edit
reproducer
Reduced from kernel miscompilation, but reproduces with user-space asan as
well.
gcc version 7.0.1 20170307 (experimental) (GCC)
Last Changed Rev: 245952
Last Changed Date: 2017-03-07 15:13:10 +0100 (Tue, 07 Mar 2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79912
--- Comment #11 from Eric Botcazou ---
> I recommend that on balance for all targets the current behavior is a
> reasonable compromise. I have said elsewhere that I am happy to continue
> working in this area and would welcome any further help
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72783
felix changed:
What|Removed |Added
CC||felix.von.s at posteo dot de
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79796
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79876
--- Comment #9 from Dominique d'Humieres ---
> I have read people complaining about very low OMP stack sizes
> on OSX.
What is setting the limit?
> Should we set this to a more reasonable default value in libgfortran?
> Less than 800k is quite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79796
--- Comment #8 from Marek Polacek ---
Author: mpolacek
Date: Tue Mar 7 17:42:30 2017
New Revision: 245957
URL: https://gcc.gnu.org/viewcvs?rev=245957=gcc=rev
Log:
PR c++/79796 - ICE with NSDMI and this pointer
* call.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79809
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79809
--- Comment #9 from Marek Polacek ---
Author: mpolacek
Date: Tue Mar 7 17:30:53 2017
New Revision: 245955
URL: https://gcc.gnu.org/viewcvs?rev=245955=gcc=rev
Log:
PR middle-end/79809
* gimple-ssa-warn-alloca.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79943
Bug ID: 79943
Summary: Loop splitting breaks with loops of pointer type
Product: gcc
Version: tree-ssa
Status: UNCONFIRMED
Severity: critical
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79888
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
In this testcase we have
C c = bar (X{1});
which store_init_value sees as
c = TARGET_EXPR i}>)>
i.e. we're initializing "c" with a TARGET_EXPR. We call replace_placeholders
that walks the whole tree to substitute the placeholders. Eventually we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79484
Segher Boessenkool changed:
What|Removed |Added
CC||segher at gcc dot gnu.org
On 03/06/2017 02:44 PM, Marek Polacek wrote:
This is an ICE with -fsanitize=undefined on invalid code involving old-style
parameter declarations and nested functions. Ugh.
Old-style parameter declarations cannot have initializers, and start_decl
errors when it sees that something's trying to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79623
Segher Boessenkool changed:
What|Removed |Added
Status|WAITING |RESOLVED
CC|
1 - 100 of 228 matches
Mail list logo