https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68466
Andreas Schwab changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
On Sat, Nov 21, 2015 at 11:41:51AM +0100, Paul Richard Thomas wrote:
>
> Just a couple of small typos:
> "Unexpected expr_type cause an ICE" ; causes?
> "! An array of derived types workd too." ; works?
>
> Apart from that it's OK for trunk.
>
> Thanks for the patch
>
Thanks for the the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68227
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
> > this patchs fixes few issues in ipa-icf. First I drop the use of
> > TYPE_CANONICAL because that is no longer part of type compatibility
> > machinery.
>
> That doesn't seem right, as the check on TYPE_CANONICAL was restored for
> aggregate types because of the serious issues we found.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63326
--- Comment #15 from Chen Gang ---
For me, comment #9 is the reasonable fixing way. In real world, C/C++
programmers will/should not use #pragma in this way (use #pragma in place of
the statement following an if, while, do, switch, or label).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66320
Martin Sebor changed:
What|Removed |Added
CC||ryan.burn at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68464
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
Hi,
this patch fixes an ICE seen with Ada LTO bootstrap in reporting type mismatches
and it also makes us to stop complaining about C++ ODR violation. The warnings
are however correct. I looked at few:
../../libiberty/xstrerror.c:40:14: warning: type of �strerror� does not match
original
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68473
Bug ID: 68473
Summary: [6 Regression] ICE: in contains_point, at
diagnostic-show-locus.c:340 after error
Product: gcc
Version: 6.0
Status: UNCONFIRMED
On 11/20/2015 3:55 PM, David Wohlferd wrote:
On 11/20/2015 8:14 AM, Richard Henderson wrote:
On 11/20/2015 04:34 PM, Jakub Jelinek wrote:
Isn't that going to break too much code though? I mean, e.g. including
libgcc...
I don't know. My suspicion is very little.
But that's actually what
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63491
Segher Boessenkool changed:
What|Removed |Added
CC||segher at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42979
--- Comment #3 from Chen Gang ---
For "The taskwait directive may not be used in place of the statement following
an if, while, do, switch, or label."
if "if, while, do, switch, or label" is just flowed with a code block which let
"#pragma omp
This patch fixes CLZ. It always returns SImode, we should look at the input
operand to determine the type. Fixes cc.c-torture/execute/builtin-bitops-1.c
committed.
nathan
2015-11-21 Nathan Sidwell
* config/nvptx/nvptx.md (clz2): Use operand 1 for type.
Index:
On Sat, Nov 21, 2015 at 10:07:35AM -0800, H.J. Lu wrote:
> On Sat, Nov 21, 2015 at 8:26 AM, Steve Kargl
> wrote:
> > On Sat, Nov 21, 2015 at 11:41:51AM +0100, Paul Richard Thomas wrote:
> >>
> >> Just a couple of small typos:
> >> "Unexpected expr_type cause an
On Sat, 21 Nov 2015, Richard Biener wrote:
On November 20, 2015 8:58:15 PM GMT+01:00, Jason Merrill
wrote:
In this bug, we hit the (A & sign-bit) != 0 -> A < 0 transformation.
Because of delayed folding, the operands aren't fully folded yet, so we
have NOP_EXPRs around
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68466
angelo changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
In investigating some failures, I noticed the PTX output is rather dense.
Committed this to add some blank lines before DECL and DEF lines. Also fixed
a few formatting inconsistencies I noticed on the way.
nathan
2015-11-21 Nathan Sidwell
* config/nvptx/nvptx.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66573
--- Comment #7 from Joshua Green ---
(In reply to Segher Boessenkool from comment #6)
> bb-reorder changes the conditional branch so that the fallthrough path
> is the most likely. It now also does this for -O1. This is faster on
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68470
Markus Trippelsdorf changed:
What|Removed |Added
Target|amd86 |
Status|UNCONFIRMED
o-fortran-checking-yes-rtl-df/
--without-cloog --without-ppl --without-isl
Thread model: posix
gcc version 6.0.0 20151121 (experimental) (GCC)
Tested revisions:
r230703 - ICE
On Fri, Nov 20, 2015 at 6:47 PM, Michael Meissner
wrote:
> On Fri, Oct 02, 2015 at 02:04:48PM -0500, Peter Bergner wrote:
>> PR67808 exposes a problem with the constraints in the *extenddftf2_internal
>> pattern, in that it allows TFmode operands to occupy Altivec
On Tue, 17 Nov 2015, Hurugalawadi, Naveen wrote:
Please find attached the patch that moves some more division optimizations
from fold-const using match and simplify.
First, note that we are in stage 3, so this all may have to wait until
sometime around March or April next year unless it is
On Sat, 21 Nov 2015, Jonathan Wakely wrote:
> I forgot to respond to this, and never committed the patch, sorry.
>
> I've committed the changes to htdocs/projects/cxx0x.html now, but
> not the htdocs/bugs/index.html change.
I wasn't opposed to the bugs/index.html change, mind. Only
wondering
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68432
--- Comment #6 from rsandifo at gcc dot gnu.org
---
The problem is with the size/speed-dependent FAILs.
I've been working on a fix, but unfortunately it's going to
be quite invasive (though hopefully makes things cleaner).
++-4.9.x
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-4_9-branch/configure
--prefix=/opt/software/x86_64/gcc-4.9.x --program-suffix=-4.9.x
--enable-languages=c,c++,fortran --enable-checking
Thread model: posix
gcc version 4.9.4 20151121 (prerelease) (GCC)
COLLECT_GCC_OPTIONS='-v' '-std
ead model: posix
gcc version 6.0.0 20151121 (experimental) (GCC)
The compiler has DF checking enabled, but it might be not needed to reproduce.
Tested revisions:
r230703 - ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68470
Markus Trippelsdorf changed:
What|Removed |Added
Keywords||ice-on-valid-code
Known to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63635
Segher Boessenkool changed:
What|Removed |Added
CC||segher at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63326
--- Comment #16 from Chen Gang ---
Our C++ has no this issue. For precisely saying: cc1 has the issue, but cc1plus
has no the issue (if use g++ build c programs, it has no issue; if use gcc
build c++ programs, it has no issue, either).
But
On Sat, Nov 21, 2015 at 8:26 AM, Steve Kargl
wrote:
> On Sat, Nov 21, 2015 at 11:41:51AM +0100, Paul Richard Thomas wrote:
>>
>> Just a couple of small typos:
>> "Unexpected expr_type cause an ICE" ; causes?
>> "! An array of derived types workd too." ; works?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68464
ryan.burn at gmail dot com changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68466
--- Comment #7 from angelo ---
Created attachment 36795
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36795=edit
gcc build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68466
--- Comment #6 from angelo ---
Created attachment 36794
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36794=edit
gcc configure
I've committed this to fix gcc.dg/atomic-generic.c. It was calling memcmp
without a declaration in scope, and passing a plain int as the 3rd argument
instead of directly using sizeof or casting to size_t. This blew up PTX with a
type mismatch.
nathan
2015-11-21 Nathan Sidwell
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68464
--- Comment #3 from ryan.burn at gmail dot com ---
Also, the test case attached to 223901 compiles fine for me.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68471
--- Comment #1 from Zdenek Sojka ---
Created attachment 36797
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36797=edit
another testcase, with __builtin_apply()
$ gcc -mmitigate-rop testcase.c
testcase.c: In function 'foo':
[ was: Re: [Committed] Mark *.omp_data_i as non-trapping ]
On 13/07/15 11:49, Tom de Vries wrote:
[ was: Re: [gomp4, committed] Handle nested loops in kernels regions ]
On 13/07/15 10:36, Jakub Jelinek wrote:
On Mon, Jul 13, 2015 at 10:19:56AM +0200, Thomas Schwinge wrote:
We rely on
On Tue, Nov 17, 2015 at 3:12 PM, David Malcolm wrote:
> On Tue, 2015-11-17 at 16:24 +0100, Bernd Schmidt wrote:
>> On 11/17/2015 04:13 PM, David Malcolm wrote:
>> > On Mon, 2015-11-16 at 22:34 +0100, Bernd Schmidt wrote:
>> >>
>> >> Should c_expr perhaps acquire a constructor
On 11/19/2015 5:53 PM, Sandra Loosemore wrote:
On 11/19/2015 06:23 PM, David Wohlferd wrote:
About the only immediate task would be to ensure that the
documentation for traditional asms clearly documents the desired
semantics and somehow note that there are known bugs in the
implementation (ie
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68298
Aditya Patil <0362ae15 at opayq dot com> changed:
What|Removed |Added
CC||0362ae15 at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49065
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #2
On November 22, 2015 2:52:53 AM GMT+01:00, David Edelsohn
wrote:
>PowerPC was missing a definition of the lroundMN pattern, which can be
>implemented with VSX instructions available in Power7. Below is a
>first draft.
>
>- David
>
>* config/rs6000/rs6000.md (*xsrdpidf2): New
PowerPC was missing a definition of the lroundMN pattern, which can be
implemented with VSX instructions available in Power7. Below is a
first draft.
- David
* config/rs6000/rs6000.md (*xsrdpidf2): New define_insn.
(lrounddfdi2): New define_expand.
diff --git a/gcc/config/rs6000/rs6000.md
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66573
--- Comment #8 from Segher Boessenkool ---
(In reply to Joshua Green from comment #7)
> and I see no reason why expecting the "else" block should a priori be
> preferable in either case.
GCC does some fairly involved prediction (in predict.c).
On Sat, Nov 21, 2015 at 11:19:22AM -0800, H.J. Lu wrote:
> On Sat, Nov 21, 2015 at 10:20 AM, Steve Kargl
> wrote:
> > On Sat, Nov 21, 2015 at 10:07:35AM -0800, H.J. Lu wrote:
> >> On Sat, Nov 21, 2015 at 8:26 AM, Steve Kargl
> >>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68442
--- Comment #3 from Dominique d'Humieres ---
The following patch
--- ../_clean/gcc/fortran/interface.c 2015-10-30 17:52:25.0 +0100
+++ gcc/fortran/interface.c 2015-11-21 23:48:11.0 +0100
@@ -3475,7 +3475,9 @@
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68470
Mikhail Maltsev changed:
What|Removed |Added
CC||miyuki at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53548
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #2
When implementing interrupt attribute for x86 interrupt handlers, we
have a difficult time to access interrupt data passed down by x86
processors. On x86, interrupt handlers are only called by processors
which push interrupt data onto stack at the address where the normal
return address is.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52828
Segher Boessenkool changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45689
Dominique d'Humieres changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48344
Segher Boessenkool changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
On Sat, 2015-11-21 at 13:54 -0500, David Edelsohn wrote:
> On Tue, Nov 17, 2015 at 3:12 PM, David Malcolm wrote:
> > On Tue, 2015-11-17 at 16:24 +0100, Bernd Schmidt wrote:
> >> On 11/17/2015 04:13 PM, David Malcolm wrote:
> >> > On Mon, 2015-11-16 at 22:34 +0100, Bernd
‘dm’ is actually not used, the building problem is fixed by the patch (I did
not rearrange the nested ‘if’s)
--- ../_clean/gcc/fortran/simplify.c2015-11-21 20:59:57.0 +0100
+++ gcc/fortran/simplify.c 2015-11-21 21:06:30.0 +0100
@@ -1792,7 +1792,6 @@ gfc_expr *
On Sat, Nov 21, 2015 at 09:22:40PM +0100, Dominique d'Humi??res wrote:
> ???dm??? is actually not used, the building problem is fixed by the patch (I
> did not rearrange the nested ???if???s)
>
> --- ../_clean/gcc/fortran/simplify.c 2015-11-21 20:59:57.0 +0100
> +++
On Sat, Nov 21, 2015 at 10:20 AM, Steve Kargl
wrote:
> On Sat, Nov 21, 2015 at 10:07:35AM -0800, H.J. Lu wrote:
>> On Sat, Nov 21, 2015 at 8:26 AM, Steve Kargl
>> wrote:
>> > On Sat, Nov 21, 2015 at 11:41:51AM +0100, Paul
configure --enable-checking=yes,rtl,df
--enable-languages=c,c++,lto,fortran
--prefix=/mnt/svn/gcc-trunk//binary-230703-lto-fortran-checking-yes-rtl-df/
--without-cloog --without-ppl --without-isl
Thread model: posix
gcc version 6.0.0 20151121 (experimental) (GCC)
Tested revisions:
r230703 - ICE
5-branc
Bug 42121 - g++ should warn or error on internal 0 size array in
struct, is a request to diagnose declarations of flexible array
members that aren't last in the enclosing struct, such as in the
following:
struct S
{
int a;
char b[]; // invalid
int c;
};
The
> + * simplify.c (gfc_simplify_cshift): Work around bootstrap issues
> + due to inappropriate warning options.
The warning options are appropriate, any dead code can potentially hide a bug
and should be flagged; every static analyzer will also do it and we would soon
have PRs opened
On Sat, Nov 21, 2015 at 11:26:17PM +0100, Eric Botcazou wrote:
> > + * simplify.c (gfc_simplify_cshift): Work around bootstrap issues
> > + due to inappropriate warning options.
>
> The warning options are appropriate, any dead code can potentially hide a bug
> and should be flagged; every
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68478
Bug ID: 68478
Summary: flexible array members have complete type
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49788
Segher Boessenkool changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
> > >
> > > Perhaps, bootstrap needs to set appropriate warning levels.
> >
> > https://gcc.gnu.org/ml/gcc-regression/2015-11/msg00648.html
> >
>
> See 5 lines up.
>
Committed.
Index: ChangeLog
===
--- ChangeLog (revision
lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /mnt/svn/gcc-trunk//configure --enable-checking=yes,rtl,df
--enable-languages=c,c++,lto,fortran
--prefix=/mnt/svn/gcc-trunk//binary-230703-lto-fortran-checking-yes-rtl-df/
--without-cloog --without-ppl --without-isl
Thread model: pos
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68476
Bug ID: 68476
Summary: microblaze: compilation of btSoftBody.cpp doesn't
terminate with optimisation
Product: gcc
Version: 5.2.1
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68477
Bug ID: 68477
Summary: error: type variant differs by TYPE_STRING_FLAG.
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On Sat, Nov 21, 2015 at 3:00 PM, David Malcolm wrote:
> On Sat, 2015-11-21 at 13:54 -0500, David Edelsohn wrote:
>> On Tue, Nov 17, 2015 at 3:12 PM, David Malcolm wrote:
>> > On Tue, 2015-11-17 at 16:24 +0100, Bernd Schmidt wrote:
>> >> On 11/17/2015
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68466
--- Comment #9 from angelo ---
Hi Andreas,
thanks. Not sure if i have to open another bug tracking. Now, with headers in
sysroot, issue is solved so this bug can stay closed, but i get another error.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67882
Martin Sebor changed:
What|Removed |Added
Status|REOPENED|SUSPENDED
--- Comment #9 from Martin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49065
Segher Boessenkool changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45208
Segher Boessenkool changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68479
Bug ID: 68479
Summary: Dynamic loading multiple shared libraries with
identical static libstdc++ breaks streams
Product: gcc
Version: 5.2.1
Status: UNCONFIRMED
On Sat, Nov 21, 2015 at 4:03 PM, David Edelsohn wrote:
> Graphite relies on the ISL library and includes multiple ISL headers.
> The ISL headers refer to identifiers that are poisoned for use in GCC.
> The source files for Graphite were organized to include the ISL
> headers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54959
Tom Tromey changed:
What|Removed |Added
CC||tromey at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50329
Segher Boessenkool changed:
What|Removed |Added
CC||segher at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66573
--- Comment #9 from Joshua Green ---
(In reply to Segher Boessenkool from comment #8)
> GCC does some fairly involved prediction (in predict.c). It isn't
> "a priori".
>
> > (It's also not clear HOW this could be "faster
> > on essentially all
Graphite relies on the ISL library and includes multiple ISL headers.
The ISL headers refer to identifiers that are poisoned for use in GCC.
The source files for Graphite were organized to include the ISL
headers first, to avoid the identifier poisoning, which breaks some
platforms because GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65413
Segher Boessenkool changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68432
--- Comment #5 from Markus Trippelsdorf ---
Started with r230487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66432
--- Comment #10 from Jakub Jelinek ---
Author: jakub
Date: Sat Nov 21 08:26:00 2015
New Revision: 230703
URL: https://gcc.gnu.org/viewcvs?rev=230703=gcc=rev
Log:
PR debug/66432
* tree-inline.c (copy_debug_stmt): If
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66432
--- Comment #9 from Jakub Jelinek ---
Author: jakub
Date: Sat Nov 21 08:24:13 2015
New Revision: 230702
URL: https://gcc.gnu.org/viewcvs?rev=230702=gcc=rev
Log:
PR debug/66432
* tree-inline.c (copy_debug_stmt): If
On 13/11/15 12:39, Jakub Jelinek wrote:
On Fri, Nov 13, 2015 at 12:29:51PM +0100, Richard Biener wrote:
thanks for the explanation. Filed as PR68331 - '[meta-bug] fipa-pta issues'.
Any feedback on the '#pragma GCC offload-alias=' bit above?
Is that sort of what you had in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68432
Markus Trippelsdorf changed:
What|Removed |Added
CC||trippels at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68466
--- Comment #1 from angelo ---
Sorry, forgot to mention compiler i am using to build:
$ gcc --version
gcc (Debian 5.2.1-21) 5.2.1 20151003
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying
On 20/11/15 11:28, Richard Biener wrote:
On Thu, 19 Nov 2015, Tom de Vries wrote:
>On 17/11/15 15:53, Tom de Vries wrote:
> > >And the above LIM example
> > >is none for why you need two LIM passes...
> >
> >Indeed. I'm planning a separate reply to explain in more detail the need
> >for the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64579
Segher Boessenkool changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|
[1] still says in its third paragraph:
--q--
Important: GCC's support for C++11 is still experimental. Some
features were implemented based on early proposals, and no attempt
will be made to maintain backward compatibility when they are updated
to match the final C++11 standard.
--/q--
[1]
> I fixed this with the below patch. Tested on x86_64 linux, x86_64 darwin and
> my port. If you want to
> list aarch64/arn and mips, please do.
>
> * g++.dg/init/vbase1.C: Only run on x86_64-*-* as this testcase
> isn't portable.
I have added i?86-*-* to the list.
2015-11-21 Uros Bizjak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68468
--- Comment #2 from Waldemar Brodkorb ---
This happens even with --enable-sjlj-exceptions.
This small hack let me create a compiler which I am trying to
use to resurrect uClibc support:
diff -Nur gcc-git.orig/libgcc/config.host
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68290
Eric Botcazou changed:
What|Removed |Added
Depends on||68434
--- Comment #4 from Eric Botcazou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68468
--- Comment #1 from Waldemar Brodkorb ---
Created attachment 36793
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36793=edit
full build log from build system
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68466
Andreas Schwab changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
On 06/10/15 12:39 -0400, Gerald Pfeifer wrote:
On Tue, 6 Oct 2015, Jonathan Wakely wrote:
People are being scared off by the experimental status on
https://gcc.gnu.org/projects/cxx0x.html
e.g. https://gcc.gnu.org/ml/gcc/2015-10/msg00025.html
This makes it clear C++11 in 5.1 is no longer
On Sat, Nov 21, 2015 at 02:16:49AM -0500, Jason Merrill wrote:
> On 11/19/2015 03:46 PM, Jason Merrill wrote:
> >On 11/15/2015 12:01 AM, David Malcolm wrote:
> >>As with the C frontend, there's an issue with tree nodes that
> >>don't have locations: VAR_DECL, INTEGER_CST, etc:
> >>
> >> int test
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Chinese (simplified) team of translators. The file is available at:
http://translationproject.org/latest/gcc/zh_CN.po
(This file,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68466
Andreas Schwab changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
> this patchs fixes few issues in ipa-icf. First I drop the use of
> TYPE_CANONICAL because that is no longer part of type compatibility
> machinery.
That doesn't seem right, as the check on TYPE_CANONICAL was restored for
aggregate types because of the serious issues we found.
> Second I also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68468
Bug ID: 68468
Summary: frv toolchain build error
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68466
angelo changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
Hi Steve,
Just a couple of small typos:
"Unexpected expr_type cause an ICE" ; causes?
"! An array of derived types workd too." ; works?
Apart from that it's OK for trunk.
Thanks for the patch
Cheers
Paul
On 20 November 2015 at 21:09, Steve Kargl
wrote:
>
1 - 100 of 107 matches
Mail list logo