public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Sebastian Huber <sh@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r11-10174] RTEMS: Do not define _GNU_SOURCE by default Date: Mon, 25 Jul 2022 13:01:48 +0000 (GMT) [thread overview] Message-ID: <20220725130148.592A43875A21@sourceware.org> (raw) https://gcc.gnu.org/g:750324e5320a3065175aed6a1b64afc8a342e79f commit r11-10174-g750324e5320a3065175aed6a1b64afc8a342e79f Author: Sebastian Huber <sebastian.huber@embedded-brains.de> Date: Fri Jul 22 14:09:20 2022 +0200 RTEMS: Do not define _GNU_SOURCE by default gcc/ChangeLog: * config/rs6000/rtems.h (CPLUSPLUS_CPP_SPEC): Undef. (cherry picked from commit 556b816b820f6749910784cbaca8bb0bb822a970) Diff: --- gcc/config/rs6000/rtems.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/gcc/config/rs6000/rtems.h b/gcc/config/rs6000/rtems.h index 872cc2849af..bd2271f94b9 100644 --- a/gcc/config/rs6000/rtems.h +++ b/gcc/config/rs6000/rtems.h @@ -23,6 +23,9 @@ see the files COPYING3 and COPYING.RUNTIME respectively. If not, see <http://www.gnu.org/licenses/>. */ +/* Undef gnu-user.h macro we don't want. */ +#undef CPLUSPLUS_CPP_SPEC + /* Copy and paste from linux64.h and freebsd64.h */ #ifdef IN_LIBGCC2 #undef TARGET_64BIT
reply other threads:[~2022-07-25 13:01 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220725130148.592A43875A21@sourceware.org \ --to=sh@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).