Pinging again, this is needed for the Windows Java VM to compile under gcc
On Wed, Sep 13, 2023 at 11:09 AM Julian Waters
wrote:
> Second desperate ping for patch
> https://gcc.gnu.org/pipermail/gcc-patches/2023-August/627913.html
>
Second desperate ping for patch
https://gcc.gnu.org/pipermail/gcc-patches/2023-August/627913.html
Hi all, this is a gentle ping for the following patch:
https://gcc.gnu.org/pipermail/gcc-patches/2023-August/627913.html
Please review the second version of a patch to add clang's invalid-noreturn
flag to toggle noreturn warnings. This patch keeps the old behaviour of
always warning on every noreturn violation, but unlike clang also adds an
extra layer of fine tuning by turning invalid-noreturn into a warning with
l
Anyone?
On Sun, Aug 13, 2023 at 4:48 PM Julian Waters
wrote:
> Please review a patch to add clang's invalid-noreturn flag to toggle
> noreturn warnings. This patch keeps the old behaviour of always warning on
> every noreturn violation, but unlike clang also adds an extra layer of fine
> tuning
Please review a patch to add clang's invalid-noreturn flag to toggle
noreturn warnings. This patch keeps the old behaviour of always warning on
every noreturn violation, but unlike clang also adds an extra layer of fine
tuning by turning invalid-noreturn into a warning with levels, where level
1 w
Hi all,
I've revised the change to be much neater
>From 480954bc7d2b24e5d19a98260a2be0b49e112c42 Mon Sep 17 00:00:00 2001
From: TheShermanTanker
Date: Wed, 28 Jun 2023 19:11:34 +0800
Subject: [PATCH] asm not using extended syntax should always be volatile
---
gcc/cp/parser.cc | 2 +-
1 file ch
gcc's documentatation mentions that all basic asm blocks are always volatile,
yet the parser fails to account for this by only ever setting
volatile_p to true
if the volatile qualifier is found. This patch fixes this by adding a
special case check for extended_p before finish_asm_stmt is called
>F
