public inbox for
 help / color / mirror / Atom feed
From: Olivier Hainque <>
To: gcc-patches <>
Cc: Olivier Hainque <>
Subject: [patch] comment about HAVE_INITFINI_ARRAY_SUPPORT in vxworks.h
Date: Thu, 29 Sep 2022 17:09:16 +0200	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 332 bytes --]


This change simply adds a comment in vxworks.h, describing
our expectations wrt our use of HAVE_INITFINI_ARRAY_SUPPORT
from this header.

Committing to mainline shortly.



2022-09-29  Olivier Hainque  <>

	* config/vxworks.h: Add comment on our use of

[-- Attachment #2: 0006-Comment-about-HAVE_INITFINI_ARRAY_SUPPORT-in-vxworks.patch --]
[-- Type: application/octet-stream, Size: 1169 bytes --]

From 423f71247294799c10960ec3be37a2544526f912 Mon Sep 17 00:00:00 2001
From: Olivier Hainque <>
Date: Thu, 10 Mar 2022 10:53:27 +0000
Subject: [PATCH 06/18] Comment about HAVE_INITFINI_ARRAY_SUPPORT in vxworks.h

Explain that we rely on compiler .c files
including auto-host.h before target configuration headers.
 gcc/config/vxworks.h | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/gcc/config/vxworks.h b/gcc/config/vxworks.h
index c18a0f65529..f2103def448 100644
--- a/gcc/config/vxworks.h
+++ b/gcc/config/vxworks.h
@@ -19,6 +19,11 @@ You should have received a copy of the GNU General Public License
 along with GCC; see the file COPYING3.  If not see
 <>.  */
+/* ??? We use HAVE_INITFINI_ARRAY_SUPPORT in preprocessor guards in this
+   header, which is conveyed by auto-host.h despite being a target property.
+   #include auto-host.h here would trigger lots of conflicts so we rely on
+   compiler .c files doing this before target configuration headers.  */
 /* Assert that we are targeting VxWorks.  */

                 reply	other threads:[~2022-09-29 15:09 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).