From: Baruch Burstein <bmburstein@gmail.com>
To: gcc@gcc.gnu.org
Subject: Fwd: Request easy bug fix
Date: Sun, 30 Oct 2022 17:01:38 +0200 [thread overview]
Message-ID: <CA+34VNKJ=j+7MNsFmXm3NwChtwKVcs=BeFBoX6_MjDLQb1YYuw@mail.gmail.com> (raw)
In-Reply-To: <CA+34VNKHGGJAD8BX4COBKrb5H-_pPm2s0ZHwMStVJqmNjTPVig@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
On Tue, Feb 15, 2022 at 5:20 PM Jonathan Wakely <jwakely.gcc@gmail.com>
wrote:
>
>
> On Tue, 15 Feb 2022 at 13:58, David Malcolm <dmalcolm@redhat.com> wrote:
>
>> On Tue, 2022-02-15 at 12:55 +0000, Jonathan Wakely via Gcc wrote:
>> > On Tue, 15 Feb 2022 at 12:34, Baruch Burstein via Gcc <
>> > gcc@gcc.gnu.org>
>> > wrote:
>> >
>> > > Hi,
>> > >
>> > > I hope it is not inappropriate to call attention to a specific bug.
>> > > https://gcc.gnu.org/bugzilla//show_bug.cgi?id=85487.
>
>
<snip>
>
Clang and the MSVC compiler both ignore any tokens after the pragma, so
> that seems good enough for GCC too:
>
> https://godbolt.org/z/norv947a5
>
>
I am sorry for posting this again, but to the best of my understanding of
the thread at https://gcc.gnu.org/bugzilla//show_bug.cgi?id=85487, the
patch already exists (I am not sure where), and was not merged to GCC 12
only because I called attention to it too late in the dev cycle, so I am
trying to get this in earlier for GCC 13. It is literally a "do-nothing"
patch.
next prev parent reply other threads:[~2022-10-30 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 12:33 Baruch Burstein
2022-02-15 12:55 ` Jonathan Wakely
2022-02-15 13:58 ` David Malcolm
2022-02-15 15:20 ` Jonathan Wakely
[not found] ` <CA+34VNKHGGJAD8BX4COBKrb5H-_pPm2s0ZHwMStVJqmNjTPVig@mail.gmail.com>
2022-10-30 15:01 ` Baruch Burstein [this message]
2022-10-31 14:03 ` Jonathan Wakely
2022-10-31 14:23 ` Baruch Burstein
2022-11-01 18:39 ` Fwd: " Jeff Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+34VNKJ=j+7MNsFmXm3NwChtwKVcs=BeFBoX6_MjDLQb1YYuw@mail.gmail.com' \
--to=bmburstein@gmail.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).