https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63303
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63304
Andrew Pinski changed:
What|Removed |Added
Target||aarch64
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63306
Bug ID: 63306
Summary: [4.9 Regression] ICE: Segmentation fault in
analyze_functions()
Product: gcc
Version: 4.9.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63306
Markus Trippelsdorf changed:
What|Removed |Added
Last reconfirmed||2014-9-19
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63244
--- Comment #11 from Markus Trippelsdorf ---
(In reply to Markus Trippelsdorf from comment #10)
> The testcase from comment 4 started segfaulting with r202298.
I've opened PR63306 for this issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63301
Andreas Schwab changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63294
--- Comment #2 from Valery Weber ---
the problem is the same as 61952
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63294
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61952
--- Comment #2 from Dominique d'Humieres ---
*** Bug 63294 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62662
--- Comment #7 from Andreas Krebbel ---
Author: krebbel
Date: Fri Sep 19 09:14:59 2014
New Revision: 215381
URL: https://gcc.gnu.org/viewcvs?rev=215381&root=gcc&view=rev
Log:
2014-09-19 Andreas Krebbel
PR target/62662
* config/s390/s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60420
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62662
--- Comment #8 from Andreas Krebbel ---
Author: krebbel
Date: Fri Sep 19 09:20:38 2014
New Revision: 215383
URL: https://gcc.gnu.org/viewcvs?rev=215383&root=gcc&view=rev
Log:
2014-09-19 Andreas Krebbel
PR target/62662
* config/s390/s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58328
--- Comment #4 from Paolo Carlini ---
Thus, I'm going to add to the testsuite both testcases as ill-formed and
closing the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63186
--- Comment #5 from Dan Horák ---
Jan, can you backport the fix also to 4.9? It is causing a problem in Fedora
where at least one build is failing due this problem.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58328
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58328
--- Comment #5 from paolo at gcc dot gnu.org ---
Author: paolo
Date: Fri Sep 19 09:34:14 2014
New Revision: 215386
URL: https://gcc.gnu.org/viewcvs?rev=215386&root=gcc&view=rev
Log:
2014-09-19 Paolo Carlini
PR c++/58328
* g++.dg/cpp0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61951
Paolo Carlini changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63307
Bug ID: 63307
Summary: [4.9/5 Regression] Cilk+ breaks -fcompare-debug
bootstrap
Product: gcc
Version: 4.9.1
Status: UNCONFIRMED
Severity: normal
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63295
Jonathan Wakely changed:
What|Removed |Added
Keywords||memory-hog
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63308
Bug ID: 63308
Summary: internal compiler error: Segmentation fault
Product: gcc
Version: 4.8.2
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63304
Richard Earnshaw changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63308
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63309
Bug ID: 63309
Summary: internal compiler error: Segmentation fault
Product: gcc
Version: 4.8.2
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63152
--- Comment #3 from vondele at gcc dot gnu.org ---
Author: vondele
Date: Fri Sep 19 10:28:00 2014
New Revision: 215387
URL: https://gcc.gnu.org/viewcvs?rev=215387&root=gcc&view=rev
Log:
2014-09-19 Joost VandeVondele
PR fortran/63152
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63152
Joost VandeVondele changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60421
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31247
--- Comment #15 from Jonathan Wakely ---
(In reply to Marc Glisse from comment #10)
> that's exactly what you'll test, since iterator_traits is not guaranteed to
> be sfinae-friendly.
N.B. that's changed for C++14.
I'm still not motivated to im
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51008
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51618
Jonathan Wakely changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62046
--- Comment #1 from Paolo Carlini ---
I think it can be reduced like this:
void foo() { } catch (...);
class bar { void foo() { } catch (...); };
we reject only the former.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53626
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56437
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56785
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57953
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55394
--- Comment #3 from Jonathan Wakely ---
related to PR 58929
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58929
--- Comment #7 from Jonathan Wakely ---
related to PR 55394
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60624
Waldemar Brodkorb changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59192
Jonathan Wakely changed:
What|Removed |Added
Severity|normal |enhancement
--- Comment #7 from Jonath
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59987
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60176
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Version|unknown
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60278
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60396
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60333
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63309
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63309
--- Comment #2 from Jonathan Wakely ---
*** Bug 63308 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63308
Jonathan Wakely changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31247
--- Comment #16 from Marc Glisse ---
(In reply to Jonathan Wakely from comment #15)
> I'm still not motivated to implement this request though.
It would break too much code.
If people really insisted (which they don't), I believe it would be sa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58192
--- Comment #8 from Uroš Bizjak ---
(In reply to Jakub Jelinek from comment #7)
> That is to be determined. Either it might be an x86_64 bug in passing such
> types, or FE issue, middle-end.
Please note that the error also occurs with -m32, so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63310
Bug ID: 63310
Summary: Ada bootstrap error with -fcompare-debug
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63310
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |4.9.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54354
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |5.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58192
--- Comment #9 from Uroš Bizjak ---
Looking at dumps, obtained with -m32 -O1, we have following sequence before the
call to _ZN2S1Ut_3setE3Foo:
_.dfinit:
(insn 7 3 8 2 (parallel [
(set (reg:SI 88)
(lshiftrt:SI (reg/v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63301
--- Comment #2 from Marcos Diaz ---
Sorry, I expressed wrong the issue I was reporting, What I want to ask is the
following:
Is it ok that the wchar_t is a long int and the wint_t is just an int?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58266
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60662
--- Comment #4 from Jonathan Wakely ---
Probably related to PR 55394
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61041
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61426
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62169
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44882
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #14 from Domi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54392
Jonathan Wakely changed:
What|Removed |Added
Blocks||24882
Target Milestone|4.8.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53221
Jonathan Wakely changed:
What|Removed |Added
Blocks||24882
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61458
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58968
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #5 from Domin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53874
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55963
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
Jonathan Wakely changed:
What|Removed |Added
CC||corey at octayn dot net
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56993
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63303
--- Comment #2 from mikulas at artax dot karlin.mff.cuni.cz ---
Jakub Jelinek: I know, but the problem happened in perfectly valid program.
Suppose that you do:
char *p = malloc(0x2000); - the allocator allocates the array at
0x7000.
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63306
Jan Hubicka changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63303
Jakub Jelinek changed:
What|Removed |Added
CC||jason at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60940
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |5.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60555
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |5.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62219
--- Comment #2 from Paolo Carlini ---
I think I had in mind c++/60605
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63304
--- Comment #5 from Venkataramanan ---
We got inspired by this bug.
https://bugs.linaro.org/show_bug.cgi?id=400
It happens at -O0 now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58192
--- Comment #10 from Jakub Jelinek ---
When I compile:
#ifdef CHAR
typedef unsigned char Foo;
#else
enum class Foo : unsigned char { FOO };
#endif
unsigned int v1, v2;
__attribute__((noinline, noclone)) static void
foo (Foo a)
{
v1 = (unsigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63301
Joel Sherrill changed:
What|Removed |Added
CC||joel at gcc dot gnu.org
--- Comment #3 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61998
--- Comment #6 from Markus Trippelsdorf ---
Author: trippels
Date: Fri Sep 19 14:44:09 2014
New Revision: 215392
URL: https://gcc.gnu.org/viewcvs?rev=215392&root=gcc&view=rev
Log:
PR ipa/61998 Fix crash -Wsuggest-final-types crash
-Wsuggest-fin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61998
Markus Trippelsdorf changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63304
Richard Earnshaw changed:
What|Removed |Added
Priority|P3 |P5
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63311
Bug ID: 63311
Summary: [4.9/5 Regression] -O1 optimization introduces
valgrind warning
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63312
Bug ID: 63312
Summary: FAIL: gcc.dg/torture/float128-exact-underflow.c -O0
execution test
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56993
--- Comment #10 from H.J. Lu ---
Created attachment 33517
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33517&action=edit
Here is my spec 2006 patch
I need this patch on x86.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63313
Bug ID: 63313
Summary: ICE in ipa-comdats.c:371
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63305
H.J. Lu changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63303
--- Comment #4 from mikulas at artax dot karlin.mff.cuni.cz ---
... and another related problem (try this on 32-bit system):
#include
#include
int main(void)
{
short *a = malloc(0x5000 * sizeof(short));
short *b = a + 0x500
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63303
--- Comment #5 from Jakub Jelinek ---
(In reply to mikulas from comment #4)
> ... and another related problem (try this on 32-bit system):
>
> #include
> #include
>
> int main(void)
> {
> short *a = malloc(0x5000 * sizeof(short));
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63303
--- Comment #6 from mikulas at artax dot karlin.mff.cuni.cz ---
"you really can't have an object bigger than half of the address space in
C/C++" - where does the standard claim this? If this is true, we should change
malloc so that it doesn't allo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63303
--- Comment #7 from joseph at codesourcery dot com ---
Yes, I consider it a bug in malloc that it produces objects 2GB or more in
size on 32-bit systems (because of the one-past-end address, the largest
size that can't produce undefined behavio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63300
Andreas Krebbel changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63303
--- Comment #8 from Jakub Jelinek ---
(In reply to mikulas from comment #6)
> Regarding pointer difference, the C standard says this:
>
> When two pointers are subtracted, both shall point to elements of the same
> array object, or one past the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63312
--- Comment #1 from Joseph S. Myers ---
Created attachment 33519
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33519&action=edit
Untested patch
Please try this patch. As I noted in my patch posting, the issue is that there
is no ia64 def
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63310
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63286
--- Comment #2 from Dominique d'Humieres ---
> I am testing:
> Index: tree.c
> ...
AFAICT the patch in comment 1 does not fix the PR.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63303
--- Comment #9 from mikulas at artax dot karlin.mff.cuni.cz ---
> See what I wrote, any object size bigger than half of address space really
> isn't supportable, because then (char *) (P) - (char *) (Q) might not fit into
> ptrdiff_t. There is no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63244
Cary Coutant changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63314
Bug ID: 63314
Summary: valarray mask/indices refers to temporary
Product: gcc
Version: 4.8.2
Status: UNCONFIRMED
Severity: blocker
Priority: P3
Component: libstd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63300
--- Comment #2 from Mark Wielaard ---
Sorry about that. I added an explicit testcases
(gcc/testsuite/gcc.dg/guality/const-volatile.c and
gcc/testsuite/gcc.dg/guality/restrict.c) explicitly to catch such issue. But
apparently they didn't trigger t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63304
Venkataramanan changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63304
Andrew Pinski changed:
What|Removed |Added
Status|RESOLVED|NEW
Resolution|WONTFIX
1 - 100 of 128 matches
Mail list logo