https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77323
--- Comment #3 from Marek Polacek ---
Author: mpolacek
Date: Thu Aug 25 08:22:56 2016
New Revision: 239752
URL: https://gcc.gnu.org/viewcvs?rev=239752&root=gcc&view=rev
Log:
PR c/77323
* c-decl.c (declspecs_add_type): Set typespe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77323
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77351
--- Comment #3 from Thomas Koenig ---
Hi steve,
> Thou shalt not derefernce NULL pointers.
Correct.
The patch is pre-approved (alternatively, it could be
considered obvious and simple).
Thanks!
Regards
Thomas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71506
Tom de Vries changed:
What|Removed |Added
CC||vries at gcc dot gnu.org
--- Comment #3 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69604
Vittorio Zecca changed:
What|Removed |Added
CC||zeccav at gmail dot com
--- Comment #10
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77363
Jiří Engelthaler changed:
What|Removed |Added
Known to work||5.3.0
--- Comment #2 from Jiří Engelt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77363
--- Comment #3 from Jiří Engelthaler ---
This pr68162 breaks the function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71506
--- Comment #4 from Tom de Vries ---
At the first call to build_linearized_memory_access, at the 3rd loop iteration
we have:
...
(gdb)
133 subsize = isl_set_max_val (pdr->extent, aff);
(gdb) call (char *)
isl_printer_get_str(isl_printe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71506
--- Comment #5 from Tom de Vries ---
(In reply to Martin Liška from comment #2)
> Current trunk, as well as GCC 6.1.1 works fine.
This is a problem in loop-interchange.c, which was removed in the 6 release
(https://gcc.gnu.org/ml/gcc-patches/201
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71700
--- Comment #6 from ktkachov at gcc dot gnu.org ---
Author: ktkachov
Date: Thu Aug 25 09:26:15 2016
New Revision: 239754
URL: https://gcc.gnu.org/viewcvs?rev=239754&root=gcc&view=rev
Log:
[expr.c] PR middle-end/71700: zero-extend sub-word value w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71700
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71506
Tom de Vries changed:
What|Removed |Added
Target Milestone|--- |5.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77377
Bug ID: 77377
Summary: [7 Regression] c-c++-common/pr59037.c ICEs with -fpic
-msse on i686
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71506
--- Comment #6 from Tom de Vries ---
Hmm, at r225942 I read:
...
[graphite] fix pr61929
This fixes bootstrap of GCC with BOOT_CFLAGS="-g -O2 -fgraphite-identity
-floop-nest-optimize -floop-block -floop-interchange -floop-strip-mine". It
passes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77369
--- Comment #1 from Jonathan Wakely ---
Richard Smith realized that it uses the noexceptness of the first type it's
instantiated with, because if you reverse the order of the calls, it produces
false, false
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77377
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |7.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77374
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |6.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77373
Richard Biener changed:
What|Removed |Added
Keywords||ice-on-valid-code
--- Comment #2 from R
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77375
Jonathan Wakely changed:
What|Removed |Added
Keywords||wrong-code
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77375
Jonathan Wakely changed:
What|Removed |Added
Known to work||4.6.4
Summary|constant obje
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69047
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71506
--- Comment #7 from Tom de Vries ---
(In reply to Tom de Vries from comment #6)
> Hmm, at r225942 I read:
Patch applies cleanly to 5 branch and fixes ICEs for original and minimal
test-cases.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69047
--- Comment #5 from Richard Biener ---
Created attachment 39498
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39498&action=edit
patch
Patch queued for testing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77377
Uroš Bizjak changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77377
--- Comment #1 from Uroš Bizjak ---
It looks that cse2 pass attaches wrong REG_EQUAL note:
(insn 8 4 13 2 (set (reg:SI 93)
(mem/u/j:SI (plus:SI (reg:SI 87)
(const:SI (plus:SI (unspec:SI [
(
Hi Guys,
The ia64-elf and i386-elf targets currently fail to build for me using
the mainline sources. The symptom is a seg-fault when running the
self tests:
./xgcc <...> -xc -S -c /dev/null -fself-test
: internal compiler error: Segmentation fault
The cause appears to be an att
On Thu, 25 Aug 2016, Nick Clifton wrote:
> The cause appears to be an attempt to register a builtin type using
> the float128_type_node, which is NULL for these particular targets:
>
> gcc/config/ia64/ia64.c:10373
> gcc/config/i386/i386.c:33347
>
> Presumably float128_type_node sho
On Thu, 25 Aug 2016, Joseph Myers wrote:
> _Float128). Though preferable would be to fix all the targets with
> IX86_NO_LIBGCC_TFMODE / IX86_MAYBE_NO_LIBGCC_TFMODE /
> IA64_NO_LIBGCC_TFMODE so that they include the relevant support code in
> libgcc and so no longer need the TARGET_LIBGCC_FLOAT
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71959
Nathan Sidwell changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72863
--- Comment #7 from Bill Schmidt ---
Author: wschmidt
Date: Thu Aug 25 14:24:17 2016
New Revision: 239761
URL: https://gcc.gnu.org/viewcvs?rev=239761&root=gcc&view=rev
Log:
[gcc]
2016-08-25 Bill Schmidt
Backport from mainline
Hi Guys,
> I think this indicates that i386 and ia64 need their own local version of
> float128_type_node, set up like float80_type_node (i.e. copied from the
> global one if that isn't NULL, otherwise set up locally) instead of using
> the global one unconditionally, because of the existence o
On Thu, 25 Aug 2016, Nick Clifton wrote:
> gcc/ChangeLog
> 2016-08-25 Nick Clifton
>
> * config/ia64/ia64.c (ia64_init_builtins): Initialise the
> float128_type_node if that has not been done already.
> * config/i386/i386.c (ix86_init_builtin_types): Likewise.
No, this is wr
Hi Joseph,
>> * config/ia64/ia64.c (ia64_init_builtins): Initialise the
>> float128_type_node if that has not been done already.
>> * config/i386/i386.c (ix86_init_builtin_types): Likewise.
>
> No, this is wrong. The global node must remain as NULL when the type is
> not fully su
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77377
H.J. Lu changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
--- Comment #2 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72863
--- Comment #8 from Bill Schmidt ---
Author: wschmidt
Date: Thu Aug 25 16:12:23 2016
New Revision: 239762
URL: https://gcc.gnu.org/viewcvs?rev=239762&root=gcc&view=rev
Log:
[gcc]
2016-08-25 Bill Schmidt
Backport from mainline (minus
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72863
Bill Schmidt changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69427
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77378
Bug ID: 77378
Summary: [7 Regression] tree-profile and libgcov assume long
long atomic operations are supported
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Ke
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77378
David Edelsohn changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77378
--- Comment #2 from Andrew Pinski ---
libatomic should provide the functions.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77327
--- Comment #7 from Fritz Reese ---
(In reply to Vittorio Zecca from comment #5)
> The test case you propose, dec_structure_13.f90, does not trigger the asan
> memory checker.
Sorry if it was unclear, the new testcase dec_structure_13.f90 tests a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67737
--- Comment #9 from Vittorio Zecca ---
(In reply to Andrew Pinski from comment #8)
> (In reply to Vittorio Zecca from comment #7)
> > With gcc 6.1.0, maybe a shorter reproducer
> > /* gcc -fcheck-pointer-bounds -mmpx p.c */
>
> That is a differe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77383
Bug ID: 77383
Summary: -fcheck-pointer-bounds -mmpx ICE in make_decl_rtl at
varasm.c
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67776
--- Comment #1 from Andrew Pinski ---
(In reply to David from comment #0)
> While not particularly interesting of itself, this makes me wonder what
> other c error checking might be getting skipped in c++.
Or rather the code is in the C front-en
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61409
--- Comment #22 from Aldy Hernandez ---
Created attachment 39499
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39499&action=edit
untested patch v1
I think I see what Jeff is getting at.
Here is an untested patch exploring the idea of ign
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77384
Bug ID: 77384
Summary: Assembler error - std::forward(decimal64) already
declared
Product: gcc
Version: 6.2.0
Status: UNCONFIRMED
Severity: normal
Pri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67733
Andrew Pinski changed:
What|Removed |Added
Target|*-*-solaris*|
Summary|elfdump and readelf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67737
--- Comment #8 from Andrew Pinski ---
(In reply to Vittorio Zecca from comment #7)
> With gcc 6.1.0, maybe a shorter reproducer
> /* gcc -fcheck-pointer-bounds -mmpx p.c */
That is a different issue and should be filed separately if not already.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77380
Bug ID: 77380
Summary: ICE in gfc_check_dependency, at
fortran/dependency.c:1255
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priori
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77380
--- Comment #1 from Gerhard Steinmetz
---
No ICE with -fcoarray=single :
$ gfortran-7-20160821 -O2 -fcoarray=single z1.f90
z1.f90:3:14:
z(:)[1] = z(:)[*]
1
Error: Coindex of codimension 1 must be a scalar at (1)
Bailed ou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77351
--- Comment #4 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Thu Aug 25 19:35:46 2016
New Revision: 239763
URL: https://gcc.gnu.org/viewcvs?rev=239763&root=gcc&view=rev
Log:
2016-08-25 Steven g. Kargl
PR fortran/77351
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77381
Bug ID: 77381
Summary: ICE in resolve_equivalence, at fortran/resolve.c:15149
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77351
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77382
--- Comment #1 from Gerhard Steinmetz
---
With official releases (configured with --enable-checking=release),
down to at least 4.8 :
$ gfortran-6 z1.f90
z1.f90:4:0:
call s
internal compiler error: in expand_expr_real_1, at expr.c:9651
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77382
Bug ID: 77382
Summary: ICE: verify_gimple failed -- expand_expr_real_1, at
expr.c:9651
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77378
--- Comment #3 from David Edelsohn ---
-ftree-profile and gcov don't link against libatomic.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77379
Bug ID: 77379
Summary: incorrect mangling for non-virtual adjustor thunk
(missing abi tag)
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77327
--- Comment #8 from Vittorio Zecca ---
Yes, it seems to me that import4.f90 is sufficient to trigger the asan
memory checker.
How strange, even without "implicit none" the loader should have complained
that "sub2" was referenced but undefined. T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77380
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77385
Bug ID: 77385
Summary: "Unclassifiable statement" from gfortran
Product: gcc
Version: 6.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77381
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77382
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77386
Bug ID: 77386
Summary: Explicit constructor is allowed causing ambiguous
initialization call when it shouldn't be allowed
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77387
Bug ID: 77387
Summary: Value range not computed in some cases for ABS_EXPR
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77387
--- Comment #1 from kugan at gcc dot gnu.org ---
With :
diff --git a/gcc/tree-vrp.c b/gcc/tree-vrp.c
index e4d789b..2d1f4c8 100644
--- a/gcc/tree-vrp.c
+++ b/gcc/tree-vrp.c
@@ -3416,6 +3416,17 @@ extract_range_from_unary_expr_1 (value_range *vr,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77387
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
--- Comment #2 from
66 matches
Mail list logo
