public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108493] Interaction with builtin_defines (on PowerPC) and -traditional-cpp Date: Mon, 23 Jan 2023 12:14:56 +0000 [thread overview] Message-ID: <bug-108493-4-PFarlZ7ZE7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108493-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108493 Iain Sandoe <iains at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Target| |powerpc-darwin, | |powerpc64-linux-gnu Component|modula2 |target Status|UNCONFIRMED |NEW Last reconfirmed| |2023-01-23 Assignee|gaius at gcc dot gnu.org |unassigned at gcc dot gnu.org Summary|Interaction with implicit |Interaction with |includes and |builtin_defines (on |-traditional-cpp |PowerPC) and | |-traditional-cpp --- Comment #2 from Iain Sandoe <iains at gcc dot gnu.org> --- this repeats on linux-gnu. There are the following defines in gcc/config/rs6000/rs6000-c.cc (conditional on !iso) : builtin_define ("vector=vector"); builtin_define ("pixel=pixel"); builtin_define ("bool=bool"); builtin_define ("_Bool=_Bool"); they've been there since 2008 .. so I guess no-one cares ( until the modula-2 case triggers it ).
next prev parent reply other threads:[~2023-01-23 12:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-23 11:07 [Bug modula2/108493] New: Interaction with implicit includes " iains at gcc dot gnu.org 2023-01-23 11:33 ` [Bug modula2/108493] " iains at gcc dot gnu.org 2023-01-23 12:14 ` iains at gcc dot gnu.org [this message] 2024-01-29 7:35 ` [Bug target/108493] Interaction with builtin_defines (on PowerPC) " gaius at gcc dot gnu.org
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=bug-108493-4-PFarlZ7ZE7@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).