public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-10033] [vxworks] avoid mangling __STDC_VERSION_LIMITS_H__
Date: Fri, 19 Apr 2024 05:57:44 +0000 (GMT)	[thread overview]
Message-ID: <20240419055744.1B102386F440@sourceware.org> (raw)

https://gcc.gnu.org/g:694fa3717a908317e895543d949eb7180911615a

commit r14-10033-g694fa3717a908317e895543d949eb7180911615a
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Fri Apr 19 02:52:21 2024 -0300

    [vxworks] avoid mangling __STDC_VERSION_LIMITS_H__
    
    The mangling of the macro name that guards limits.h from reinclusion
    was mangling a c23-required macro as well.  Make the edit pattern
    stricter.
    
    
    for  gcc/ChangeLog
    
            * config/t-vxworks (vxw-glimits.h): Don't mangle c23-required
            __STDC_VERSION_LIMITS_H__ define.

Diff:
---
 gcc/config/t-vxworks | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/config/t-vxworks b/gcc/config/t-vxworks
index b89350c3c70..6063943e346 100644
--- a/gcc/config/t-vxworks
+++ b/gcc/config/t-vxworks
@@ -57,7 +57,7 @@ T_GLIMITS_H = vxw-glimits.h
 
 vxw-glimits.h: $(srcdir)/glimits.h
 	ID=`echo $(BASEVER_c) | sed -e 's/\./_/g'` && \
-	sed -e "s/_LIMITS_H__/_LIMITS_H__$${ID}_/" < $< > $@T
+	sed -e "s/_LIMITS_H___/_LIMITS_H__$${ID}_/" < $< > $@T
 	mv $@T $@
 
 # Arrange to "provide" a tailored version of stdint-gcc.h

                 reply	other threads:[~2024-04-19  5:57 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=20240419055744.1B102386F440@sourceware.org \
    --to=aoliva@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: 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).