Dear all,
the attached patch is pretty much self-explaining: check for bounds violation
when initializing a substring in a data statement and treat the resulting error.
If more detailed information should be emitted with the error message, I'm
open for suggestions.
Regtested on x86_64-pc-linux-g
On Tue, Jan 19, 2021 at 11:28 PM Jason Merrill wrote:
>
> On 1/10/21 7:28 PM, Paul Fee via Gcc-patches wrote:
> > [PATCH v2] c++: Add support for -std=c++2b
>
> Thanks!
>
> This patch was corrupted by word wrap, so it won't apply; if you can't
> suppress word wrap in your mail client, please send
Derived from the changes that added C++2a support in 2017.
https://gcc.gnu.org/g:026a79f70cf33f836ea5275eda72d4870a3041e5
No C++23 features are added here.
Use of -std=c++23 sets __cplusplus to 202100L.
$ g++ -std=c++23 -dM -E -x c++ - < /dev/null | grep cplusplus
#define __cplusplus 202100L
Cha
On Fri, 22 Jan 2021, Jakub Jelinek wrote:
> Hi!
>
> As mentioned in the PR, the compiler behaves differently during strncmp
> and strncasecmp folding between 32-bit and 64-bit hosts targeting 64-bit
> target. I think that is highly undesirable.
>
> The culprit is the host_size_t_cst_p predicate
On Fri, 22 Jan 2021, Segher Boessenkool wrote:
> On Fri, Jan 22, 2021 at 02:47:06PM +0100, Richard Biener wrote:
> > On Thu, 21 Jan 2021, Segher Boessenkool wrote:
> > > What is holding up this patch still? Ke Wen has pinged it every month
> > > since May, and there has still not been a review.
>
