https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68286
Richard Biener changed:
What|Removed |Added
Version|unknown |6.0
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68285
Richard Biener changed:
What|Removed |Added
Target||x86_64-*-*
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68065
--- Comment #25 from Daniel Micay ---
> Just as GCC on Windows...
Sure. I'm pointing out that Windows has had safety here for years, while Linux
doesn't. It should. It really shouldn't be possible to exploit well-defined
code. Running out of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64267
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68065
--- Comment #26 from Eric Botcazou ---
> Sure. I'm pointing out that Windows has had safety here for years, while
> Linux doesn't.
Thanks for correcting, the initial formulation was quite misleading and could
be understood as GCC not being on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67826
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68271
--- Comment #12 from Dominique d'Humieres ---
Is the problem that difficult to fix?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68272
Sergey Organov changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68291
Bug ID: 68291
Summary: [6 regression] ICE in emit_move_insn, at expr.c:3540
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58497
Rainer Orth changed:
What|Removed |Added
CC||ro at gcc dot gnu.org
--- Comment #5 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68286
--- Comment #1 from Markus Trippelsdorf ---
Started with r230098.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68283
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68283
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66756
--- Comment #3 from Dominique d'Humieres ---
> but why do set the status on waiting ? Is there any question implied ?
Yes. In a perfect world, someone else would have to confirm it. In GCC land,
you can change the status to NEW if you still see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64651
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68271
--- Comment #13 from Jakub Jelinek ---
Quick temporary fix is easy, just make pragma_kind in cp/parser.h 8 bit, and
change id < 64 to id < 256 in c-family and update the comment. This I believe
shouldn't make the C++ token any larger.
And then
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68292
Rainer Orth changed:
What|Removed |Added
Target Milestone|--- |6.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68292
Bug ID: 68292
Summary: [6 regression] ICE in copy_blkmode_to_reg, at
expr.c:2277
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68283
Joost VandeVondele changed:
What|Removed |Added
Keywords||ice-on-invalid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68285
Uroš Bizjak changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68268
--- Comment #4 from Dominique d'Humieres ---
Executing "./configure ..." means you are bootstrapping in the sources
directory which is not supported according the manual. You must create a build
directory, cd to it, and execute
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68234
Jiong Wang changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68289
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68234
--- Comment #5 from Jiong Wang ---
Author: jiwang
Date: Wed Nov 11 10:51:31 2015
New Revision: 230150
URL: https://gcc.gnu.org/viewcvs?rev=230150=gcc=rev
Log:
[Patch] PR tree-optimization/68234 Improve range info for loop Phi node
2015-11-11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68289
Manuel López-Ibáñez changed:
What|Removed |Added
CC|manu at gcc dot gnu.org|
--- Comment #4 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68282
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66388
amker at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58497
--- Comment #6 from Rainer Orth ---
The new gcc.dg/tree-ssa/vector-5.c testcase FAILs on 64-bit Solaris/SPARC:
FAIL: gcc.dg/tree-ssa/vector-5.c scan-tree-dump-times optimized " * 3;" 1
Rainer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67826
--- Comment #4 from dominiq at gcc dot gnu.org ---
Author: dominiq
Date: Wed Nov 11 10:30:25 2015
New Revision: 230148
URL: https://gcc.gnu.org/viewcvs?rev=230148=gcc=rev
Log:
2015-11-11 Dominique d'Humieres
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53934
Bug 53934 depends on bug 44054, which changed state.
Bug 44054 Summary: Handle -Werror, -Werror=, -fdiagnostics-show-option, !GCC$
diagnostic (pragmas) and color
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44054
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68289
Bug ID: 68289
Summary: Missing diagnostic pragmas
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68283
--- Comment #4 from Manuel López-Ibáñez ---
(In reply to Dominique d'Humieres from comment #3)
>
> With revision r216098 (2014-10-10) it gives
This seems a problem with the buffering of errors that Fortran does. I might
have missed some cases.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68284
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68290
Rainer Orth changed:
What|Removed |Added
Target Milestone|--- |6.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68290
Bug ID: 68290
Summary: g++.dg/concepts/auto1.C FAILs
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
tdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-230151-checking-yes-rtl-df-nographite-aarch64
Thread model: posix
gcc version 6.0.0 2015 (experimental) (GCC)
Tested revisions:
r230151 - ICE
r230115 - ICE
r230014 - OK
4_5-branch r230093 - OK
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64651
--- Comment #1 from Jonathan Wakely ---
Author: redi
Date: Wed Nov 11 10:08:23 2015
New Revision: 230147
URL: https://gcc.gnu.org/viewcvs?rev=230147=gcc=rev
Log:
PR libstdc++/64651
* libsupc++/exception_ptr.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68289
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68291
Markus Trippelsdorf changed:
What|Removed |Added
CC||ienkovich at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68275
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68287
--- Comment #1 from Martin Liška ---
Started from r230027 which is my commit, sorry for the noise, I'm going to fix
it.
Martin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58189
Bug 58189 depends on bug 44054, which changed state.
Bug 44054 Summary: Handle -Werror, -Werror=, -fdiagnostics-show-option, !GCC$
diagnostic (pragmas) and color
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44054
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44054
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68289
--- Comment #3 from Dominique d'Humieres ---
> > IMO implementing the diagnostic pragmas in gfortran will just be a waste of
> > time. Thus if someone want to close this PR as WONTFIX, I won't object!
>
> Why? Doesn't Fortran have pragmas?
Yes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68272
Sergey Organov changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68291
Rainer Orth changed:
What|Removed |Added
Target Milestone|--- |6.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68282
sgunderson at bigfoot dot com changed:
What|Removed |Added
CC||sgunderson at bigfoot dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68269
Segher Boessenkool changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68277
--- Comment #1 from Kazumoto Kojima ---
Created attachment 36686
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36686=edit
reduced test case for -O1
It fails on trunk too. It seems that the problematic add insn
(insn 765 764 300 46 (set
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67305
--- Comment #9 from Jiong Wang ---
Author: jiwang
Date: Wed Nov 11 12:30:46 2015
New Revision: 230158
URL: https://gcc.gnu.org/viewcvs?rev=230158=gcc=rev
Log:
[ARM] PR67305, tighten neon_vector_mem_operand on eliminable registers
2015-11-11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58497
--- Comment #8 from Rainer Orth ---
Created attachment 36687
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36687=edit
-fdump-tree-dom2-details dump
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68271
--- Comment #14 from Dominique d'Humieres ---
> Quick temporary fix is easy, just make pragma_kind in cp/parser.h 8 bit,
> and change id < 64 to id < 256 in c-family and update the comment.
> This I believe shouldn't make the C++ token any
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68138
--- Comment #1 from Ville Voutilainen ---
The test works if operator== is not a member. There's something fairly fishy
going on here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56592
--- Comment #4 from Oleg Endo ---
(In reply to Oleg Endo from comment #0)
>
> Function argument/return value aggregates are decomposed so that the
> individual members can be passed in different register classes, based on the
> data type. E.g.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68299
Bug ID: 68299
Summary: [5/6 Regression] runtime error: member call on null
pointer of type 'const struct __lambda0'
Product: gcc
Version: 5.2.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68300
Bug ID: 68300
Summary: Bogus -Wnon-virtual-dtor warning with protected base
class constructor
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68299
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66205
simon at pushface dot org changed:
What|Removed |Added
Attachment #35567|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60158
--- Comment #5 from joakim.tjernlund at transmode dot se ---
I am sure I saw .data.rel.ro.local section with a .4byte statement in it
using -S
Now I cannot repeat it. The only thing that has changed that I know is
glibc 2.19 is no glibc 2.20
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68283
--- Comment #7 from Steve Kargl ---
On Wed, Nov 11, 2015 at 06:01:19PM +, dominiq at lps dot ens.fr wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68283
>
> --- Comment #6 from Dominique d'Humieres ---
> For some reason, the ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68298
Bug ID: 68298
Summary: wrong code at -O3 on x86_64-linux-gnu (in 64-bit mode)
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60421
--- Comment #9 from Jonathan Wakely ---
(In reply to Jaak Ristioja from comment #6)
> Additionally, the nanosleep code is also missing proper EINTR handling,
> which again could break the sleep.
This part is done.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68286
Renlin Li changed:
What|Removed |Added
Target|powerpc64le-unknown-linux-g |powerpc64le-unknown-linux-g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192
Andreas Arnez changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68299
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67941
Jonathan Wakely changed:
What|Removed |Added
CC||redi at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68062
--- Comment #6 from Marek Polacek ---
If we should pay attention to the sign, then maybe
--- gcc/c-family/c-common.c
+++ gcc/c-family/c-common.c
@@ -11903,9 +11903,9 @@ vector_types_compatible_elements_p (tree t1, tree t2)
&& (c2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68283
--- Comment #6 from Dominique d'Humieres ---
For some reason, the ICE requires to use at least -O.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60421
--- Comment #8 from Jonathan Wakely ---
Author: redi
Date: Wed Nov 11 17:08:51 2015
New Revision: 230183
URL: https://gcc.gnu.org/viewcvs?rev=230183=gcc=rev
Log:
Loop in std::this_thread sleep functions
PR libstdc++/60421
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68283
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67265
--- Comment #9 from Eric Botcazou ---
Author: ebotcazou
Date: Wed Nov 11 14:56:17 2015
New Revision: 230176
URL: https://gcc.gnu.org/viewcvs?rev=230176=gcc=rev
Log:
PR target/67265
* ira.c (ira_setup_eliminable_regset): Do not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68294
--- Comment #2 from Robert Clausecker ---
Created attachment 36689
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36689=edit
Testcase for bug #68294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68282
--- Comment #3 from Stan Shebs ---
Sorry, left out a detail - the cltq output is compilation as C++. Compiled as
a C file, the code does have the andl as noted. (I'm sure there are good
reasons why the *exact* *same* source text ends up with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68297
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68266
--- Comment #3 from Marek Polacek ---
Author: mpolacek
Date: Wed Nov 11 14:47:03 2015
New Revision: 230174
URL: https://gcc.gnu.org/viewcvs?rev=230174=gcc=rev
Log:
PR c/68107
PR c++/68266
* c-common.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68107
--- Comment #3 from Marek Polacek ---
Author: mpolacek
Date: Wed Nov 11 14:47:03 2015
New Revision: 230174
URL: https://gcc.gnu.org/viewcvs?rev=230174=gcc=rev
Log:
PR c/68107
PR c++/68266
* c-common.c
: gcc.c-torture/compile/pr53410-2.c -O0 (internal compiler error)
FAIL: gcc.c-torture/compile/pr53410-2.c -O0 (test for excess errors)
Excess errors:
/opt/gcc/gcc-2015/gcc/testsuite/gcc.c-torture/compile/pr53410-2.c:27:18:
internal compiler error: in prepare_cmp_insn, at optabs.c:3813
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68039
--- Comment #2 from Marek Polacek ---
Since op1 and op2 in that COND_EXPR are the same, we fold the conditional
expression to a COMPOUND_EXPR:
return x ();, 0;
so the result of x () looks unused.
Same for C++.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67305
Jiong Wang changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68065
--- Comment #29 from Alexander Cherepanov ---
On 2015-11-11 14:57, ebotcazou at gcc dot gnu.org wrote:
>> Are you saying that -fstack-check is ready for use? Why it's not
>> documented (except for Ada and in gccint)?
>
> !??? See 3.18 Options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68138
Ville Voutilainen changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67612
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67265
--- Comment #8 from Eric Botcazou ---
Author: ebotcazou
Date: Wed Nov 11 14:24:39 2015
New Revision: 230170
URL: https://gcc.gnu.org/viewcvs?rev=230170=gcc=rev
Log:
PR target/67265
* config/i386/i386.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68293
James Greenhalgh changed:
What|Removed |Added
CC||jgreenhalgh at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68272
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68272
--- Comment #5 from Sergey Organov ---
Thanks, but my particular problem is that I do want nice GCC builtin when it is
available, and I want generic inline implementation, rather than function call,
when GCC builtin is not available.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68062
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68297
Bug ID: 68297
Summary: Faster std::make_exception
Product: gcc
Version: 5.1.1
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68107
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68266
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68293
--- Comment #2 from Zdenek Sojka ---
(In reply to James Greenhalgh from comment #1)
> Looks related to pr68134 ?
Maybe; the compiler crashes at roughly the same place.
PR68134 is "r230014 or older", so either the buggy path is now triggered
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68294
--- Comment #3 from Robert Clausecker ---
Sorry, I forgot to attach the test case. Here it is.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67265
--- Comment #10 from Eric Botcazou ---
Author: ebotcazou
Date: Wed Nov 11 16:04:34 2015
New Revision: 230179
URL: https://gcc.gnu.org/viewcvs?rev=230179=gcc=rev
Log:
PR target/67265
* ira.c (ira_setup_eliminable_regset): Do not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67265
Eric Botcazou changed:
What|Removed |Added
Target Milestone|--- |4.9.4
--- Comment #11 from Eric
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67265
Eric Botcazou changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68287
Bug ID: 68287
Summary: [6 Regression] conditional jump or move depends on
uninitialized value in lra-lives.c:1048
Product: gcc
Version: 6.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68288
Bug ID: 68288
Summary: botched floating-point UDL
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68287
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |6.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68065
--- Comment #27 from Alexander Cherepanov ---
On 2015-11-11 11:16, ebotcazou at gcc dot gnu.org wrote:
> On 2015-11-11 03:36, danielmicay at gmail dot com wrote:
>> The implementation of -fstack-check in GCC does have significant overhead,
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58497
--- Comment #9 from rguenther at suse dot de ---
On Wed, 11 Nov 2015, ro at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58497
>
> --- Comment #8 from Rainer Orth ---
> Created attachment 36687
> -->
1 - 100 of 163 matches
Mail list logo