https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80811
--- Comment #2 from Marc Glisse ---
Reminds me of PR 59048 and some others, except that in that one adding "pure"
was not sufficient.
Is "pure" true for all legal template parameters of basic_string?
Marek Polacek writes:
> On Wed, May 17, 2017 at 09:13:40AM -0600, Jeff Law wrote:
>> On 05/17/2017 04:23 AM, Aldy Hernandez wrote:
>> > Hi folks.
>> >
>> > I've been having troubles comparing the results of different test runs
>> > for quite some time, and have finally
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66032
--- Comment #6 from Chris Johns ---
Created attachment 41380
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41380=edit
Use awk to create compile args as sed is not working on FreeBSD
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66032
--- Comment #5 from Chris Johns ---
I have decided to revisit this bug and see what the issue is. I cannot see how
to reopen the issue?
Using GNU sed on FreeBSD is not straight forward. It requires either building
by hand to a custom prefix
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80813
Bug ID: 80813
Summary: x86: std::vector::operator[] could be somewhat
faster using BT instead of SHL
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80812
Bug ID: 80812
Summary: internal compiler error: in build_value_init_noctor,
at cp/init.c:483
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80811
--- Comment #1 from Martin Sebor ---
There are typos in the example in comment #0. Here's what it should look like:
#include
void cmp (const std::string , const std::string )
{
int c1 = s1.compare (s2);
int c2 = s1.compare (s2);
if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80811
Bug ID: 80811
Summary: out-of-line string members less efficient than they
could be
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80810
Bug ID: 80810
Summary: char_traits members taking reference arguments instead
of values
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: trivial
On Wed, May 17, 2017 at 2:59 PM, Will Hawkins wrote:
> On Wed, May 17, 2017 at 2:41 PM, Will Hawkins wrote:
>> On Wed, May 17, 2017 at 1:04 PM, Will Hawkins wrote:
>>> On Wed, May 17, 2017 at 1:02 PM, Jeff Law wrote:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80777
--- Comment #5 from Julian Rose ---
https://bugzilla.redhat.com/show_bug.cgi?id=518712 describes the same issue
under Linux. But repeating the same test described in comment-1 there when run
under x86_64-pc-cygwin gets the wrong answer:
$ gdb
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80731
Martin Sebor changed:
What|Removed |Added
Keywords||patch
Assignee|unassigned at
While working on a new warning for unsafe conversion I noticed
that the existing warnings that diagnose these kinds of problems
are missing some useful detail. For example, given declarations
of an integer Type and an integer Constant defined in some header,
a C programmer who writes this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80692
Segher Boessenkool changed:
What|Removed |Added
Known to work||8.0
--- Comment #4 from Segher
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80597
--- Comment #14 from Dmitry Babokin ---
Disregard my previous comment.
Original test case still fails with compiler switches that I've originally
reported (-fsanitize=undefined).
Hi Will,
On Wed, May 17, 2017 at 01:44:45PM -0500, Will Schmidt wrote:
> --- a/gcc/testsuite/gcc.target/powerpc/fold-vec-div-floatdouble.c
> +++ b/gcc/testsuite/gcc.target/powerpc/fold-vec-div-floatdouble.c
> @@ -1,9 +1,9 @@
> /* Verify that overloaded built-ins for vec_div with float and
> -
Snapshot gcc-6-20170517 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20170517/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6
On 05/17/2017 04:56 PM, Bill Schmidt wrote:
Hi Nathan,
Interestingly, this patch applies cleanly, but does *not* solve the problem
with libgo.
Another puzzling development, since bisection showed all revisions before this
being clean and all revisions afterward being problematic. Drat. :(
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80692
--- Comment #3 from Segher Boessenkool ---
Author: segher
Date: Wed May 17 21:57:23 2017
New Revision: 248174
URL: https://gcc.gnu.org/viewcvs?rev=248174=gcc=rev
Log:
Fix comparison of decimal float zeroes (PR80692)
Decimal float negative zero
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80809
Bug ID: 80809
Summary: Multi-free error for variable size array used within
OpenMP task
Product: gcc
Version: 7.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80797
--- Comment #4 from Vittorio Zecca ---
I applied your patch to version 8 trunk 247930 and it seems to work,
but on your example I get
ubsan-1.c:10:8: runtime error: member access within null pointer of type
'struct S'
ubsan-1.c:11:8: runtime
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80597
--- Comment #13 from Dmitry Babokin ---
The attached patch fixes my original test case.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80782
--- Comment #11 from René J.V. Bertin ---
I'm using 6.3.0 (that was the latest release when I started). It has the same
code in config/darwin.h though:
```
/* When we detect that we're cctools or llvm as, we need to insert the right
Hello world,
after receiving no negative feedback on my RFC patch, I have deciced
to submit the patch.
The attached patch handles MATMUL(TRANSPOSE(A),B) in inlining matmul.
Speed is a bit faster than the library version.
Regression-tested. OK for trunk?
Regards
Thomas
2017-05-17
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80808
Jakub Jelinek changed:
What|Removed |Added
Target||armv7hl-linux-gnueabi
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80808
Bug ID: 80808
Summary: [7/8 Regression] gnupg miscompilation on arm starting
with r241660
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Hi Carl,
Bunch of things, I'm afraid.
On Wed, May 17, 2017 at 08:25:38AM -0700, Carl E. Love wrote:
>* config/rs6000/rs6000-c: Add support for built-in functions
>* config/rs6000/rs6000-builtin.def: Add definitions for
>* config/rs6000/altivec.h: Add define for
Some parts are
On Wed, May 17, 2017 at 4:56 PM, Steven Munroe
wrote:
> David pointed out that I my earlier X86 BMI intrinsic header submission
> was causing make check failures on on powerpc64le platforms. The patch
> below tests out on Linux BE powerpc64/32 and should also resolve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80799
H.J. Lu changed:
What|Removed |Added
Blocks||70118
--- Comment #3 from H.J. Lu ---
This
The patch passes bootstrap+test on x86_64 and found a few functions in
the source tree (attached func_names.txt) that could be annotated with
malloc (I gave a brief look at some of the functions and didn't appear
to be false positives but I will recheck thoroughly)
virtual char*
David pointed out that I my earlier X86 BMI intrinsic header submission
was causing make check failures on on powerpc64le platforms. The patch
below tests out on Linux BE powerpc64/32 and should also resolve the
failures on AIX. I don't have access to a AIX so David can you give this
patch a quick
Hi Nathan,
Interestingly, this patch applies cleanly, but does *not* solve the problem
with libgo.
Another puzzling development, since bisection showed all revisions before this
being clean and all revisions afterward being problematic. Drat. :(
I will have to go deeper into what's happening
On 07.05.17 21:23, Andreas Tobler wrote:
Hi all,
On FreeBSD we make use of the functions _Unwind_GetIP, _Unwind_GetIPInfo
and _Unwind_SetIP outside of GCC. All other FreeBSD targets have these
functions available except arm.
Now since the GCC port for arm*-*-freebsd* is used more often (not
On Wed, May 17, 2017 at 06:36:38PM +, Segher Boessenkool wrote:
> 2017-05-17 Segher Boessenkool
>
> PR middle-end/80692
> * real.c (do_compare): Give decimal_do_compare preference over
> comparing just the signs.
>
> gcc/testsuite/
> PR
On 05/17/2017 04:11 PM, Eric Botcazou wrote:
* config/sparc/sparc.c (sparc_option_override): Set function
alignment for -mcpu=niagara7 to 64 to match the I$ line.
* testsuite/gcc.target/sparc/niagara7-align.c: Test case with
-mcpu=niagara7 -falign-functions.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80741
--- Comment #8 from Jerry DeLisle ---
Author: jvdelisle
Date: Wed May 17 20:33:34 2017
New Revision: 248172
URL: https://gcc.gnu.org/viewcvs?rev=248172=gcc=rev
Log:
2017-05-17 Jerry DeLisle
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80741
--- Comment #6 from Jerry DeLisle ---
Author: jvdelisle
Date: Wed May 17 20:33:20 2017
New Revision: 248170
URL: https://gcc.gnu.org/viewcvs?rev=248170=gcc=rev
Log:
2017-05-17 Jerry DeLisle
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80741
--- Comment #7 from Jerry DeLisle ---
Author: jvdelisle
Date: Wed May 17 20:33:27 2017
New Revision: 248171
URL: https://gcc.gnu.org/viewcvs?rev=248171=gcc=rev
Log:
2017-05-17 Jerry DeLisle
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57466
--- Comment #17 from Jonathan Wakely ---
Fine by me.
EDG agrees with GCC, but Clang accepts the original example. I guess they'll
change when 1584 gets resolved.
This libgo patch ensures that the packages vendored into the standard
library do not have the same pkgpath as the actual packages. If we
don't, attempts to build and test the actual packages will get
confused. The specific error I was seeing was import loops, causing
some of the packages to fail
> * config/sparc/sparc.c (sparc_option_override): Set function
> alignment for -mcpu=niagara7 to 64 to match the I$ line.
> * testsuite/gcc.target/sparc/niagara7-align.c: Test case with
> -mcpu=niagara7 -falign-functions.
The testsuite directory has its own ChangeLog file
> This patch series contains small fixes and updates for the SPARC
> platform.
>
> Patch 1 fixes a small typo in sol2.h
>
> Patch 2 sets a branch cost for the SPARC T4 processor.
>
> Patch 3 sets a branch cost for the SPARC M7 processor.
>
> Patch 4 changes the function alignment for the M7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78881
Jerry DeLisle changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80727
Jerry DeLisle changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57466
--- Comment #16 from Paolo Carlini ---
Shall we definitely close this, then?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80727
--- Comment #4 from Jerry DeLisle ---
Author: jvdelisle
Date: Wed May 17 20:00:53 2017
New Revision: 248167
URL: https://gcc.gnu.org/viewcvs?rev=248167=gcc=rev
Log:
2017-05-17 Jerry DeLisle
Backport from trunk
* config/sparc/sparc.h (BRANCH_COST): Set the SPARC M7 branch
latency to 1.
---
gcc/config/sparc/sparc.h |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/gcc/config/sparc/sparc.h b/gcc/config/sparc/sparc.h
index 6277738..686a3d5 100644
---
* config/sparc/sparc.c (sparc_option_override): Set function
alignment for -mcpu=niagara7 to 64 to match the I$ line.
* testsuite/gcc.target/sparc/niagara7-align.c: Test case with
-mcpu=niagara7 -falign-functions.
---
gcc/config/sparc/sparc.c
* config/sparc/sparc.h (BRANCH_COST): Set the SPARC T4 branch
latency to 2.
---
gcc/config/sparc/sparc.h |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/gcc/config/sparc/sparc.h b/gcc/config/sparc/sparc.h
index 590a5f4..6277738 100644
---
This patch series contains small fixes and updates for the SPARC
platform.
Patch 1 fixes a small typo in sol2.h
Patch 2 sets a branch cost for the SPARC T4 processor.
Patch 3 sets a branch cost for the SPARC M7 processor.
Patch 4 changes the function alignment for the M7 processor from 4 to 8
* config/sparc/sol2.h: Fix a ASM_CPU32_DEFAULT_SPEC typo.
---
gcc/config/sparc/sol2.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/gcc/config/sparc/sol2.h b/gcc/config/sparc/sol2.h
index db24ca3..8a50bfe 100644
--- a/gcc/config/sparc/sol2.h
+++
On Wed, May 17, 2017 at 2:41 PM, Will Hawkins wrote:
> On Wed, May 17, 2017 at 1:04 PM, Will Hawkins wrote:
>> On Wed, May 17, 2017 at 1:02 PM, Jeff Law wrote:
>>> On 05/17/2017 10:36 AM, Will Hawkins wrote:
As I started looking into
Review and update the dg-require-effective-target clauses
for the fold-vec-* tests. Most of the tests affected here had
specified altivec when they actually needed VSX.
Also simplified the related dg-options statements to eliminate
redundancies.
The testcases have now been double-checked in
Hi Fritz,
Yes, that's good for trunk.
Thanks
Paul
On 17 May 2017 at 16:51, Fritz Reese wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79968
>
> All,
>
> The PR suggests unifying diagnostics of the form "%s at %C is a DEC
> extension, enable with ..." I think the
On Wed, May 17, 2017 at 1:04 PM, Will Hawkins wrote:
> On Wed, May 17, 2017 at 1:02 PM, Jeff Law wrote:
>> On 05/17/2017 10:36 AM, Will Hawkins wrote:
>>> As I started looking into this, it seems like PLUGIN_FINISH is where
>>> my plugin will go. Everything
Hi Jerry,
OK for trunk and for 7-branch after a delay.
Cheers and thanks
Paul
On 17 May 2017 at 06:34, Jerry DeLisle wrote:
> Hi all,
>
> When I first looked at this I thought the minor front end bobble was the
> problem. That turns out to be unrelated but needed to be
On 05/15/17 03:39, Daniel Santos wrote:
> On 05/14/2017 11:31 AM, Bernd Edlinger wrote:
>> Hi Daniel,
>>
>> there is one thing I don't understand in your patch:
>> That is, it introduces a static value:
>>
>> /* Registers who's save & restore will be managed by stubs called from
>>
Decimal float negative zero should compare equal to positive zero.
Decimal float zeroes are encoded as value class "normal" (in real.c);
they need to be handled specially, but in this one case that does not
yet happen. This fixes it.
Bootstrapped and tested on powerpc64-linux {-m32,-m64}; also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80396
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69945
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78659
Jerry DeLisle changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68156
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78659
--- Comment #15 from Jerry DeLisle ---
Author: jvdelisle
Date: Wed May 17 18:09:48 2017
New Revision: 248166
URL: https://gcc.gnu.org/viewcvs?rev=248166=gcc=rev
Log:
2017-05-17 Jerry DeLisle
Backport from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65978
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On 05/17/2017 01:53 PM, Nathan Sidwell wrote:
Bill,
the revision you converged on is, as Ian, says, just moving some
interface around. That was needed to fix obj-c++.
This diff is the combination of that patch and its logical predecessor.
Does reverting this diff get you back to normalcy?
Bill,
the revision you converged on is, as Ian, says, just moving some
interface around. That was needed to fix obj-c++.
This diff is the combination of that patch and its logical predecessor.
Does reverting this diff get you back to normalcy?
nathan
--
Nathan Sidwell
Index:
Hi,
I apparently committed the wrong version of this file with a typo in the
dg-options. Fixed, tested on powerpc64le-unknown-linux-gnu, committed
as obvious.
Thanks,
Bill
2017-05-17 Bill Schmidt
* gcc.target/powerpc/pr78604.c: Fix typo in dg-options.
On 05/17/17 04:01, Daniel Santos wrote:
> On 05/16/2017 02:52 PM, Bernd Edlinger wrote:
>> I think I solved the problem with -fsplit-stack, I am not sure
>> if ix86_static_chain_on_stack might change after reload due to
>> final.c possibly calling targetm.calls.static_chain, but if that
>> is the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80793
--- Comment #2 from Martin Sebor ---
The warnings aren't incorrect, there are just too many of them for what boils
down to essentially the same problem. It's true that the operands of the
conditional expression have mixed signedness. It's also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80782
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62045
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80782
--- Comment #9 from Andrew Pinski ---
(In reply to René J.V. Bertin from comment #7)
> (In reply to Jonathan Wakely from comment #6)
>
> > I assume something like --with-as=llvm-as doesn't work.
>
> Nope.
What GCC version did you try? 6.x or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62045
--- Comment #14 from Jonathan Wakely ---
Author: redi
Date: Wed May 17 17:18:14 2017
New Revision: 248164
URL: https://gcc.gnu.org/viewcvs?rev=248164=gcc=rev
Log:
PR libstdc++/62045 fix O(N) insertion in pd_ds binary heap
Backport from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66059
--- Comment #16 from Jonathan Wakely ---
Author: redi
Date: Wed May 17 17:18:07 2017
New Revision: 248163
URL: https://gcc.gnu.org/viewcvs?rev=248163=gcc=rev
Log:
PR libstdc++/66059 optimise _Build_index_tuple
Backport from mainline
2015-11-17
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66059
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80782
--- Comment #8 from Andrew Pinski ---
This should be easy to do as a target specific specs. There should be already
one which is used for arguments to as.
From config/darwin.h:
410 /* When we detect that we're cctools or llvm as, we need to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52389
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80794
--- Comment #7 from Andrew Pinski ---
(In reply to Martin Sebor from comment #6)
> (In reply to Martin Sebor from comment #5)
> > S::i cannot change during the lifetime of an S object because S::i is
> > declared const. This holds regardless of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80782
--- Comment #7 from René J.V. Bertin ---
(In reply to Jonathan Wakely from comment #6)
> I assume something like --with-as=llvm-as doesn't work.
Nope.
> It would require
> configure to know how to detect the llvm assembler and know how to
On Wed, May 17, 2017 at 1:02 PM, Jeff Law wrote:
> On 05/17/2017 10:36 AM, Will Hawkins wrote:
>> As I started looking into this, it seems like PLUGIN_FINISH is where
>> my plugin will go. Everything is great so far. However, when plugins
>> at that event are invoked, they get no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80791
--- Comment #1 from amker at gcc dot gnu.org ---
Sorry for causing this, I will investigate.
Thanks,
On 05/17/2017 10:36 AM, Will Hawkins wrote:
> As I started looking into this, it seems like PLUGIN_FINISH is where
> my plugin will go. Everything is great so far. However, when plugins
> at that event are invoked, they get no data. That means I will have to
> look into global structures for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80794
--- Comment #6 from Martin Sebor ---
(In reply to Martin Sebor from comment #5)
> S::i cannot change during the lifetime of an S object because S::i is
> declared const. This holds regardless of whether the S object itself is
> const.
To be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80794
--- Comment #5 from Martin Sebor ---
S::i cannot change during the lifetime of an S object because S::i is declared
const. This holds regardless of whether the S object itself is const.
[basic.life] outlines the restrictions on creating a new
As I started looking into this, it seems like PLUGIN_FINISH is where
my plugin will go. Everything is great so far. However, when plugins
at that event are invoked, they get no data. That means I will have to
look into global structures for information regarding the compilation.
Are there pointers
On Wed, 17 May 2017, Marek Polacek wrote:
> I've always disliked using 0 where NULL_TREE should be. It's confusing to see
> if (value != 0), which makes value to look like an integer, even though it may
> be a tree.
>
> Next cleanup will probablyn be about using booleans where desirable.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80794
Michael Matz changed:
What|Removed |Added
CC||matz at gcc dot gnu.org
--- Comment #4
Nothing very interesting, I noticed a few Doxygen warnings while
building the docs.
* include/bits/refwrap.h: Fix Doxygen warning.
* include/bits/specfun.h: Likewise.
* include/bits/std_function.h: Likewise.
* include/bits/stl_algo.h (set_union, set_intersection)
On Wed, 2017-05-17 at 10:41 +0100, Bin.Cheng wrote:
> I happen to be working on loop distribution now (If guess correctly,
> to get hmmer fixed). So far my idea is to fuse the finest
> distributed
> loop in two passes, in the first pass, we merge all SCCs due to
> "true"
> data dependence; in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80807
Bug ID: 80807
Summary: Improve FORTIFY_SOURCE protection for sprintf
Product: gcc
Version: 5.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52389
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|5.5 |---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79968
Fritz Reese changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #2 from Fritz Reese
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80794
--- Comment #3 from Andrew Pinski ---
Can't S::f call inplace operator new changing the value of *this for the call
in bar?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79968
All,
The PR suggests unifying diagnostics of the form "%s at %C is a DEC
extension, enable with ..." I think the patch is obvious/trivial and
speaks for itself. I plan to commit the attached to trunk shortly,
barring any complaints.
(Nb. even
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80597
--- Comment #12 from Pat Haugen ---
(In reply to Martin Liška from comment #11)
> Created attachment 41375 [details]
> Patch candidate v2
>
> Can you please test this version? It moves e from 10^6 to 10^5.
That patch works for both the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80806
Bug ID: 80806
Summary: gcc does not warn if local array is memset only
Product: gcc
Version: 5.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
This patch breaks a bit more out of pushdecl. When pushing an extern
"C" function, we have to go check for other instances of it in different
namespaces. We had lookup_extern_c_fun_in_all_ns to go find it in a
different namespace. Looking for a name across all namespaces is the
one thing
Add warning to back end and add test.
Patch is attached.
If the patch is acceptable, I would appreciate if someone could commit
it for me as I do not have write access.
2017-05-XX Jozef Lawrynowicz
gcc/
PR target/78818
* config/msp430/msp430.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80794
Martin Sebor changed:
What|Removed |Added
Status|WAITING |UNCONFIRMED
Ever confirmed|1
Change back end and add tests.
Patch is attached.
Note: Patch will not apply if
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01030.html has been
committed. "$DEFAULT_CFLAGS" in msp430.exp would need to be changed to
"$MSP430_DEFAULT_CFLAGS".
If the patch is acceptable, I would appreciate if
1 - 100 of 241 matches
Mail list logo