public inbox for cygwin-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org> To: cygwin-cvs@sourceware.org, newlib-cvs@sourceware.org Subject: [newlib-cygwin] Fix compile time warning messages building with gcc v6.1.1 Date: Thu, 11 Nov 2021 01:15:40 +0000 (GMT) [thread overview] Message-ID: <20211111011540.083123858400@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=babc07f7ef1676f15dbeeff498c6b6a8e03ccac6 commit babc07f7ef1676f15dbeeff498c6b6a8e03ccac6 Author: Nick Clifton <nickc@redhat.com> Date: Mon Jun 13 10:49:26 2016 +0100 Fix compile time warning messages building with gcc v6.1.1 etc * texi2pod.pl: Escape curly braces, whilst searching for keyword strong. gas * config/tc-arm.c: For non-ELF based targets skip ARM feature sets that are not supported. * config/tc-arc.c (md_apply_fix): Avoid left shifting a signed constant. * config/tc-cr16.c (check_range): Likewise. * config/tc-nios2.c (nios2_check_overflow): Likewise. Diff: --- etc/ChangeLog | 5 +++++ etc/texi2pod.pl | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/etc/ChangeLog b/etc/ChangeLog index c11033826..1864bf0c8 100644 --- a/etc/ChangeLog +++ b/etc/ChangeLog @@ -1,3 +1,8 @@ +2016-06-13 Nick Clifton <nickc@redhat.com> + + * texi2pod.pl: Escape curly braces, whilst searching for keyword + strong. + 2016-03-18 Nick Clifton <nickc@redhat.com> * texi2pod.pl: Add TARGET to the list of recognised man page diff --git a/etc/texi2pod.pl b/etc/texi2pod.pl index dd3e181db..0f465b7c7 100644 --- a/etc/texi2pod.pl +++ b/etc/texi2pod.pl @@ -311,7 +311,7 @@ while(<$inf>) { @columns = (); for $column (split (/\s*\@tab\s*/, $1)) { # @strong{...} is used a @headitem work-alike - $column =~ s/^\@strong{(.*)}$/$1/; + $column =~ s/^\@strong\{(.*)\}$/$1/; push @columns, $column; } $_ = "\n=item ".join (" : ", @columns)."\n";
reply other threads:[~2021-11-11 1:15 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=20211111011540.083123858400@sourceware.org \ --to=vapier@sourceware.org \ --cc=cygwin-cvs@sourceware.org \ --cc=newlib-cvs@sourceware.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).