On 6/27/24 11:25 AM, Tamar Christina wrote:
-Original Message-
From: Jason Merrill
Sent: Tuesday, June 25, 2024 10:24 PM
To: Tamar Christina
Cc: gcc-patches@gcc.gnu.org; nd ; nat...@acm.org
Subject: Re: [PATCH][c++ frontend]: check for missing condition for novector
[PR115623]
On 6/25
> -Original Message-
> From: Jason Merrill
> Sent: Tuesday, June 25, 2024 10:24 PM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; nat...@acm.org
> Subject: Re: [PATCH][c++ frontend]: check for missing condition for novector
> [PR115623]
>
> On 6/2
On 6/25/24 12:52, Tamar Christina wrote:
The 06/25/2024 17:10, Jason Merrill wrote:
On 6/25/24 04:01, Tamar Christina wrote:
Hi All,
It looks like I forgot to check in the C++ frontend if a condition exist for the
loop being adorned with novector. This causes a segfault because cond isn't
exp
The 06/25/2024 17:10, Jason Merrill wrote:
> On 6/25/24 04:01, Tamar Christina wrote:
> > Hi All,
> >
> > It looks like I forgot to check in the C++ frontend if a condition exist
> > for the
> > loop being adorned with novector. This causes a segfault because cond isn't
> > expected to be null.
On 6/25/24 04:01, Tamar Christina wrote:
Hi All,
It looks like I forgot to check in the C++ frontend if a condition exist for the
loop being adorned with novector. This causes a segfault because cond isn't
expected to be null.
This fixes it by issuing the same kind of diagnostics we issue for
Hi All,
It looks like I forgot to check in the C++ frontend if a condition exist for the
loop being adorned with novector. This causes a segfault because cond isn't
expected to be null.
This fixes it by issuing the same kind of diagnostics we issue for the other
pragmas.
Bootstrapped Regtested
