From: Gerald Pfeifer <gerald@pfeifer.com>
To: Martin Jambor <mjambor@suse.cz>
Cc: Jakub Jelinek <jakub@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Michal Jires <mjires@suse.cz>
Subject: Re: [wwwdocs] Porting-to-14: Mention new pragma GCC Target behavior
Date: Sat, 4 May 2024 01:37:37 +0200 (CEST) [thread overview]
Message-ID: <a43e6b38-deb0-ee33-46a1-33dc3fbf1a32@pfeifer.com> (raw)
In-Reply-To: <ri6wmobyjul.fsf@virgil.suse.cz>
On Thu, 2 May 2024, Martin Jambor wrote:
> Thanks for your suggestions, this is what I am going to commit in a
> moment.
Thanks!
> diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html
>
> +<h3 id="target-pragma">Pragma GCC target now affects preprocessor symbols</h4>
A small detail I missed: <h3> closed by </h4> :-) I'll fix this in a
second.
> +<p>
> +The behavior of pragma GCC target and specifically how it affects ISA
> +macros has changed in GCC 14. In GCC 13 and older, the <code>GCC
> +target</code> pragma defined and undefined corresponding ISA macros in
> +C when using the integrated preprocessor during compilation but not
> +when the preprocessor was invoked as a separate step or when using
> +the <code>-save-temps</code> option. In C++ the ISA macro definitions
> +were performed in a way which did not have any actual effect.
> +
> +In GCC 14 C++ behaves like C with integrated preprocessing in earlier
> +versions. Moreover, in both languages ISA macros are defined and
> +undefined as expected when preprocessing separately from compilation.
I assume this should be two paragraphs? I'll make this change and some
other tweaks.
Gerald
prev parent reply other threads:[~2024-05-03 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 12:34 Martin Jambor
2024-04-25 12:41 ` Jakub Jelinek
2024-04-30 21:12 ` Martin Jambor
2024-04-30 21:30 ` Jakub Jelinek
2024-05-01 14:05 ` Gerald Pfeifer
2024-05-02 21:39 ` Martin Jambor
2024-05-03 23:37 ` Gerald Pfeifer [this message]
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=a43e6b38-deb0-ee33-46a1-33dc3fbf1a32@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mjambor@suse.cz \
--cc=mjires@suse.cz \
/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).