https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92813
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68700
Christian Biesinger changed:
What|Removed |Added
CC||cbiesinger at google dot com
---
I forgot about , so I actually committed this patch
instead.
commit 46f60e0689384ba6e58a9896b5831969940ac74b
Author: Jonathan Wakely
Date: Wed Dec 4 23:26:45 2019 +
Document some more C++20 support in libstdc++
diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
On 12/4/19 1:16 PM, Segher Boessenkool wrote:
> For future patches: it is much easier to review if you make the big,
> mechanical move a separate (earlier) patch.
Will do.
>> I have also
>> included a small patch to disable running the powerpc/dfp/ tests even for
>> powerpc*-linux when
On 03/12/19 20:30 -0500, JeanHeyd Meneide wrote:
This patch implements deprecate POD for the C++ Standard Library,
Thanks.
bringing libstdc++ that much closer to 2020 conformance !
N.B. adding the attribute is not required for conformance.
+#if defined(__DEPRECATED) && (__cplusplus >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84919
--- Comment #17 from Martin Sebor ---
The patch below avoids the warning. Unfortunately, as a result of bug 92666,
it triggers another bogus warning during bootstrap.
Index: gcc/c-family/c-common.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70517
Christian Biesinger changed:
What|Removed |Added
CC||cbiesinger at google dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88629
Christian Biesinger changed:
What|Removed |Added
CC||cbiesinger at google dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84668
Christian Biesinger changed:
What|Removed |Added
CC||cbiesinger at google dot com
---
On Wed, Dec 04, 2019 at 05:16:05PM -0600, Segher Boessenkool wrote:
> > pla 9,ext_symbol@pcrel # add (0),1 for optional operands
>
> pla does not have optional operands like that?
It does, just like load/store insns.
--
Alan Modra
Australia Development Lab, IBM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87241
Christian Biesinger changed:
What|Removed |Added
CC||cbiesinger at google dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91582
--- Comment #4 from Martin Sebor ---
Author: msebor
Date: Thu Dec 5 01:28:11 2019
New Revision: 278983
URL: https://gcc.gnu.org/viewcvs?rev=278983=gcc=rev
Log:
PR middle-end/91582 - missing heap overflow detection for strcpy
gcc/ChangeLog:
On 12/2/19 10:06 AM, Jeff Law wrote:
On 11/8/19 3:11 PM, Martin Sebor wrote:
Unless it's used with _FORTIFY_SOURCE, -Wstringop-overflow
doesn't consider out-of-bounds accesses to objects allocated
by alloca, malloc, other functions declared with attribute
alloc_size, or even VLAs with variable
Hi!
On Fri, 15 Nov 2019 13:41:11 -0800
Julian Brown wrote:
> This patch provides support for gang local storage allocation in
> shared memory. It is mostly identical to the version posted
> previously, with one cosmetic fix (a duplicated identical condition):
>
>
This libbacktrace patch adds the noclone attribute to the version of
test1 in edtest.c, to correspond to other versions of test1.
Bootstrapped and ran libbacktrace tests on x86_64-pc-linux-gnu.
Committed to mainline.
Ian
2019-12-04 Ian Lance Taylor
* edtest.c (test1): Add noclone attribute.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92815
Bug ID: 92815
Summary: spurious -Wstringop-overflow writing into a flexible
array of an extern struct
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92815
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92815
Martin Sebor changed:
What|Removed |Added
Blocks||56456
--- Comment #2 from Martin Sebor
On Wed, Dec 4, 2019 at 4:22 PM Jakub Jelinek wrote:
>
> On Wed, Dec 04, 2019 at 10:07:05AM +0800, Hongtao Liu wrote:
> > Changelog
> > gcc/
> > PR target/92686
> > * config/i386/sse.md
> > (*_cmp3,
> > *_cmp3,
> > *_ucmp3,
> > *_ucmp3): New.
> > *
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92814
Bug ID: 92814
Summary: missing -Wstringop-overflow writing into a dynamically
allocated flexible array member
Product: gcc
Version: 10.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91582
--- Comment #5 from Martin Sebor ---
Part 2 of the patch series was committed in r278983. Part 1 and part 3 are
still waiting for review and approval:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00429.html
* python/libstdcxx/v6/printers.py (StdCmpCatPrinter): New printer.
* testsuite/libstdc++-prettyprinters/cxx20.cc: New test.
Tested x86_64-linux, committed to trunk.
commit b41a87d7889f2399d4c1a0c626a656ba384e71a8
Author: Jonathan Wakely
Date: Thu Dec 5 00:24:58 2019 +
As done for std::pair, this defines operator<=> as a non-member function
template and does not alter operator==, as expected to be proposed as
the resolution to an unpublished LWG issue.
Instead of calling std::lexicographical_compare_three_way the <=>
overload is implemented by hand to take
This libbacktrace patch simplifies the DWARF section handling. This
is in preparation for DWARF 5 support, as DWARF 5 requires us to read
more sections. Bootstrapped and ran libbacktrace and Go tests on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
2019-12-04 Ian Lance Taylor
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39751
--- Comment #11 from Dmitry G. Dyachenko ---
Original test case from c#0 crash in trunk
gcc version 10.0.0 20191204 (experimental) [trunk revision 278972] (GCC)
$ g++ -fpreprocessed -fsyntax-only a.ii
a.ii:5:1: error: types may not be defined
Hi,
the inline assembly "p" modifier ("An operand that is a valid memory address is
allowed",
cf.
https://gcc.gnu.org/onlinedocs/gcc/Simple-Constraints.html#Simple-Constraints)
is not supported on AMD GCN. This causes an ICE during the compilation of
gcc.dg/asm-4.c.
We should skip the test for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92799
Richard Biener changed:
What|Removed |Added
Keywords||ice-on-valid-code
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
--- Comment #8 from Richard Biener ---
(In reply to Jakub Jelinek from comment #4)
> Though, there is another issue, for the nelts 2 vectors
> simplify_vector_constructor created code is actually larger than old code.
> And, it might be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92800
--- Comment #1 from Richard Biener ---
Note there's people from Marvell working on the same thing, posting design docs
(some privately to me though). gobl...@marvell.com was working on this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92801
--- Comment #3 from Richard Biener ---
You're repeating mistakes fromm the past. The "dumb" approach works for a
single
benchmark (mcf) but isn't at all usable for anything in the real world which
means it is of no use for GCC (when factoring
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
--- Comment #6 from Richard Biener ---
Hmm, I don't think it is fully correct. Let me dig in a bit.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
Richard Biener changed:
What|Removed |Added
Assignee|jakub at gcc dot gnu.org |rguenth at gcc dot
gnu.org
---
201 - 232 of 232 matches
Mail list logo