https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77512
--- Comment #5 from Eric Botcazou ---
What's the configure line this time?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77610
--- Comment #3 from Kazumoto Kojima ---
Created attachment 39642
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39642&action=edit
patch to add default threshold
256 sounds reasonable to me. Does the attached patch work for you?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77629
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |7.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77631
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77639
Richard Biener changed:
What|Removed |Added
Keywords||error-recovery,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77621
Jakub Jelinek changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77638
Richard Biener changed:
What|Removed |Added
Keywords||error-recovery,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77637
Richard Biener changed:
What|Removed |Added
Keywords||ice-on-invalid-code
Status|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77633
--- Comment #1 from Jakub Jelinek ---
Looking at ICC 16.0.2, it uses the same prototypes though, again with
_MM_PERM_ENUM as the type of this argument.
It is true the AVX512 manual states int rather than _MM_PERM_ENUM, so I don't
know what is rig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77637
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77637
--- Comment #3 from Marek Polacek ---
No, that's the change of default std.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77637
--- Comment #4 from Marek Polacek ---
This:
commit e829f68a9b1f4f3e34588704710c6e88f3703a28
Author: jason
Date: Fri May 8 04:42:06 2015 +
PR c++/59012
* parser.c (cp_parser_std_attribute_list): Handle attribute expansion.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77636
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77640
Bug ID: 77640
Summary: FDHBNFGJ
Product: gcc
Version: new-ra
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77512
--- Comment #6 from michael at mijobe dot org ---
../gcc-6.2.0/configure --prefix=/export/home2/mi/gcc-6.2.0-bin --with-gnu-as
--with-gnu-ld --disable-libgcj --enable-languages=c,c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77637
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77512
--- Comment #7 from Eric Botcazou ---
> ../gcc-6.2.0/configure --prefix=/export/home2/mi/gcc-6.2.0-bin --with-gnu-as
> --with-gnu-ld --disable-libgcj --enable-languages=c,c++
Please add --build=sparc-sun-solaris2.10 and use an absolute path.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77512
--- Comment #8 from michael at mijobe dot org ---
will do
think this will take roughly 8 hours ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77633
--- Comment #2 from Wenzel Jakob ---
I just tried compiling this snippet with ICC 17.0.0. It accepts it without
warnings (-Wall -Wconversion -Wextra). So even if the signature is different,
ICC seems to be more relaxed about passing an integer va
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66339
--- Comment #9 from frankhb1989 at gmail dot com ---
(In reply to Andrew Pinski from comment #8)
> (In reply to frankhb1989 from comment #7)
> > This is definitely a leak from the view of libc. Why is the status INVALID
> > instead of WONTFIX?
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66339
--- Comment #10 from Jonathan Wakely ---
This behaviour is by design and is not a bug. Valgrind no longer shows the
allocation as reachable. Other tools might still show the memory as unfreed,
but it's still not a bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66339
--- Comment #11 from Jonathan Wakely ---
(In reply to frankhb1989 from comment #9)
> Following your narrow definition of "leak", it implies that any system using
> GC could never leak. That's absurd.
Wikipedia: "a memory leak is a type of resour
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77638
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77639
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77621
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |6.3
Summary|Internal compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77633
--- Comment #3 from Jakub Jelinek ---
Does it work even if you
#define __INTEL_COMPILER_USE_INTRINSIC_PROTOTYPES 1
before including immintrin.h?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66339
--- Comment #12 from frankhb1989 at gmail dot com ---
(In reply to Jonathan Wakely from comment #10)
> This behaviour is by design and is not a bug. Valgrind no longer shows the
> allocation as reachable. Other tools might still show the memory as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77633
--- Comment #4 from Wenzel Jakob ---
Aha, interesting -- that breaks it:
test.cpp(9): error: argument of type "int" is incompatible with parameter of
type "_MM_PERM_ENUM={_MM_PERM_ENUM}"
_mm512_shuffle_epi32(_mm512_setzero_epi32(), _MM_SHU
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77621
Uroš Bizjak changed:
What|Removed |Added
Status|REOPENED|NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66514
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77558
Uroš Bizjak changed:
What|Removed |Added
CC||ubizjak at gmail dot com
--- Comment #5 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77558
--- Comment #6 from Tom de Vries ---
Patch bootstrapped and reg-tested on x86_64.
Patch build and reg-tested on arm, no issues found.
Todo: submit to gcc-patches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66491
--- Comment #3 from Andrew Pinski ---
This is how I build my gcc that is not building against a libc:
# glibc will provide ssp as it is new enough
gcc_cv_libc_provides_ssp=yes ${PMAKE} configure-gcc || return 1
This is after doing configure to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66339
--- Comment #13 from Richard Biener ---
Note the pool was made dynamic (and effectively larger) exactly for a QOI
issue...
[the dynamic nature is to make its size controllable by the environment, sth
that didn't materialize yet]
The difficulty w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77584
--- Comment #2 from foreese at gcc dot gnu.org ---
Author: foreese
Date: Mon Sep 19 11:32:09 2016
New Revision: 240230
URL: https://gcc.gnu.org/viewcvs?rev=240230&root=gcc&view=rev
Log:
2016-09-19 Fritz Reese
PR fortran/77584
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77626
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77641
Bug ID: 77641
Summary: std::variant copy-initialization fails for non-trivial
literal type
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Keywords: rejects-valid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66433
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77639
Patrick Palka changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=76731
--- Comment #5 from Jakub Jelinek ---
Kyrill/Uros, is this something we should change?
Any comments on the #c1 questions?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63299
Maxim Ostapenko changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77641
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77641
--- Comment #2 from Jonathan Wakely ---
Testing this:
--- a/libstdc++-v3/include/std/variant
+++ b/libstdc++-v3/include/std/variant
@@ -168,7 +168,7 @@ namespace __variant
template
using __storage = typename __storage_type<_Type>::type;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77641
--- Comment #3 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #1)
> std::string_view is a literal type, but is not trivially default
> constructible.
Oops, I meant X is a literal type (my original code uses variant but I redu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66391
Andrew Pinski changed:
What|Removed |Added
Component|rtl-optimization|middle-end
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77538
--- Comment #6 from Dmitry Vyukov ---
It hangs trying to dump core file to some pipe:
[] pipe_wait+0x70/0xc0
[] pipe_write+0x236/0x5b0
[] do_sync_write+0x8d/0xd0
[] dump_write+0x52/0x70
[] dump_seek+0xa4/0xe0
[] elf_core_dump+0x896/0x950
[] do_c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77642
Bug ID: 77642
Summary: GO Bootstrap fail starting with r239872 splitstack
signature does not match
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: norma
dule m
implicit none
character(len=:), pointer :: r ! works
character(len=5), pointer :: s => null() ! works
character(len=:), pointer :: p => null() ! ICE
end module m
$ gfortran --version
GNU Fortran (GCC) 7.0.0 20160919 (experimental)
$ gfortran -c m.f90
f951: inter
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71952
vehre at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77644
Bug ID: 77644
Summary: missed optimization with sqrt in comparison
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-op
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77624
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267
--- Comment #8 from Alexander Ivchenko ---
Thanks, Matthias, that's a valid point about changing linker on a runtime. In
my defense, I see that right now MPX does not work with '-fuse-ld=bfd' anyways:
>gcc test.c -fcheck-pointer-bounds -mmpx -fu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77624
--- Comment #4 from Jakub Jelinek ---
Created attachment 39647
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39647&action=edit
gcc7-pr77624-alt.patch
Alternate untested patch. The problem right now is that because these
intrinsics are pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77645
Bug ID: 77645
Summary: Python xmethods tests failing
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77621
Richard Biener changed:
What|Removed |Added
Target||x86_64-*-*, i?86-*-*
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77645
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77646
Bug ID: 77646
Summary: GCC Segfault with -O3
Product: gcc
Version: 5.4.0
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: c
Assignee: una
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77647
Bug ID: 77647
Summary: Missed opportunity to use register value causes
additional load
Product: gcc
Version: 6.2.0
Status: UNCONFIRMED
Severity: enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77646
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77352
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77646
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77587
--- Comment #5 from Jakub Jelinek ---
Author: jakub
Date: Mon Sep 19 14:36:38 2016
New Revision: 240232
URL: https://gcc.gnu.org/viewcvs?rev=240232&root=gcc&view=rev
Log:
PR target/77587
* cgraph.c (cgraph_node::rtl_info): Pass &
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77571
Richard Earnshaw changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77556
Paolo Carlini changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71827
--- Comment #4 from Paolo Carlini ---
*** Bug 77556 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77648
Bug ID: 77648
Summary: Setting conversion to a integer to double to 0 3/4
through a loop
Product: gcc
Version: 5.3.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77646
--- Comment #3 from Markus Trippelsdorf ---
Or with creduce's rename-toks:
struct e {
int (*f)();
void (*g)();
} * c;
int a;
void *h();
typedef struct { struct e j; } k;
int l() { return a; }
const struct e b = {l};
void m() {
k *d = h();
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77646
Markus Trippelsdorf changed:
What|Removed |Added
CC||trippels at gcc dot gnu.org
K
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77621
--- Comment #8 from Uroš Bizjak ---
(In reply to Richard Biener from comment #7)
> So it seems V2DFmode is available but discouraged via the above hook when
> tuning for atom.
>
> Indeed:
>
> static machine_mode
> ix86_preferred_simd_mode (mac
Fortran runtime error: Index '2' of dimension 1 of array 'text' above upper
bound of 1
$ gfortran --version
GNU Fortran (GCC) 7.0.0 20160919 (experimental)
program p
implicit none
character(len=10) :: s
s = fs((/"abc","d "/))
write(*,*) s
contains
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77642
--- Comment #1 from Andreas Krebbel ---
On s390 32 bit size_t is "unsigned long". __splitstack_find in libgcc is
defined as follows:
extern void*
__splitstack_find (void *, void *, size_t *, void **, void **, v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77338
Paolo Carlini changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77645
--- Comment #2 from Jonathan Wakely ---
Author: redi
Date: Mon Sep 19 15:49:19 2016
New Revision: 240233
URL: https://gcc.gnu.org/viewcvs?rev=240233&root=gcc&view=rev
Log:
libstdc++/77645 Fix xmethods for std::list
PR libstdc++/77645
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77645
--- Comment #3 from Jonathan Wakely ---
Author: redi
Date: Mon Sep 19 15:50:53 2016
New Revision: 240235
URL: https://gcc.gnu.org/viewcvs?rev=240235&root=gcc&view=rev
Log:
libstdc++/77645 Fix xmethods for std::list
PR libstdc++/77645
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77645
Jonathan Wakely changed:
What|Removed |Added
Summary|[6/7 Regression] Python |Python xmethods tests
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77650
Bug ID: 77650
Summary: struct with a nested flexible array followed by
another member accepted
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77648
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77647
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
Status|U
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77651
Bug ID: 77651
Summary: c++ -Wno-aligned-new ICEs
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assigne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77651
Markus Trippelsdorf changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77651
--- Comment #2 from Guille ---
Correction: There is no issue with '-faligned-new', only with
'-Wno-aligned-new'.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77645
--- Comment #5 from Jonathan Wakely ---
Author: redi
Date: Mon Sep 19 17:09:04 2016
New Revision: 240241
URL: https://gcc.gnu.org/viewcvs?rev=240241&root=gcc&view=rev
Log:
libstdc++/77645 fix deque and vector xmethods for Python 3
PR li
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77645
--- Comment #6 from Jonathan Wakely ---
Author: redi
Date: Mon Sep 19 17:14:11 2016
New Revision: 240242
URL: https://gcc.gnu.org/viewcvs?rev=240242&root=gcc&view=rev
Log:
libstdc++/77645 fix deque and vector xmethods for Python 3
PR li
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77645
--- Comment #7 from Jonathan Wakely ---
Author: redi
Date: Mon Sep 19 17:17:47 2016
New Revision: 240243
URL: https://gcc.gnu.org/viewcvs?rev=240243&root=gcc&view=rev
Log:
libstdc++/77645 fix deque and vector xmethods for Python 3
PR li
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77651
--- Comment #3 from Guille ---
Excuses, I take that back.
I use placement new on a properly aligned piece of memory, gcc complains
(warning) that:
* 'note: uses ‘void* operator new(std::size_t, void*)’, which does not have an
alignment paramet
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77645
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53659
--- Comment #4 from PeteVine ---
I've just done the obvious and run the resulting ARMv7 binaries on a Cortex A53
in aarch32 mode and the difference is there (GCC 6.2.1 and 7.0.0) so I can
confirm the issue is present to this day.
Cortex-A5 vs C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53659
--- Comment #5 from PeteVine ---
Created attachment 39649
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39649&action=edit
Annotated ARMv7 assembly
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77639
--- Comment #3 from Patrick Palka ---
Author: ppalka
Date: Mon Sep 19 18:12:36 2016
New Revision: 240245
URL: https://gcc.gnu.org/viewcvs?rev=240245&root=gcc&view=rev
Log:
Fix PR c++/77639 (ICE during error recovery)
gcc/cp/ChangeLog:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77652
Bug ID: 77652
Summary: Invalid rank error in ASSOCIATED when rank is remapped
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77652
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77651
--- Comment #4 from Guille ---
For what it's worth, any call to 'c++ -Waligned-new=none ...' will also ICE.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77648
--- Comment #2 from Raymond Fontenot ---
Created attachment 39650
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39650&action=edit
Test Case for Bug
I've attached a test case for this. The code will produce the incorrect
polynomial functio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77616
TC changed:
What|Removed |Added
CC||rs2740 at gmail dot com
--- Comment #1 from TC ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77650
--- Comment #1 from joseph at codesourcery dot com ---
On Mon, 19 Sep 2016, msebor at gcc dot gnu.org wrote:
> While testing my patch for C++ bug 71912 and gathering material for WG14 paper
> N2083 I noticed that GCC isn't completely consistent
COLLECT_LTO_WRAPPER=/usr/local/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/7.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-source-trunk/configure --enable-languages=c,c++,lto
--prefix=/usr/local/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 7.0.0 20160919 (experimental) [trunk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77648
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77654
Bug ID: 77654
Summary: restrict pointer attribute not preserved with
-fprefetch-loop-arrays
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77654
--- Comment #1 from Doug Gilmore ---
Created attachment 39651
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39651&action=edit
Additional tracing used to identify problem.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77654
--- Comment #2 from Doug Gilmore ---
Created attachment 39652
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39652&action=edit
Prototype fix for bug.
1 - 100 of 108 matches
Mail list logo
