public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/100658] Typos in dg commands and texi files
Date: Wed, 19 May 2021 13:25:27 +0000	[thread overview]
Message-ID: <bug-100658-4-v4uQjpS9lv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100658-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100658

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marxin at gcc dot gnu.org

--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
I'm going to fix the typos, thanks,

> ./gcc/testsuite/gcc.dg/cpp/lexident.c:8:/* Escaped newlines, _ and $ in
> identifiers.  */
> ./gcc/testsuite/gcc.target/i386/pr91298-1.c:4:/* { dg-xfail-if "No support
> for $ in identifiers" { *-*-solaris2.* && { ! gas } } } */
> ./gcc/testsuite/gcc.target/i386/pr91298-2.c:4:/* { dg-xfail-if "No support
> for $ in identifiers" { *-*-solaris2.* && { ! gas } } } */
> ./libcpp/charset.c:1131:          cpp_error (pfile, CPP_DL_PEDWARN, "'$' in
> identifier or number");
> ./libcpp/lex.c:1335:      cpp_error (pfile, CPP_DL_PEDWARN, "'$' in
> identifier or number");

What's wrong about the $ sign?

  parent reply	other threads:[~2021-05-19 13:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 17:39 [Bug testsuite/100658] New: " gscfq@t-online.de
2021-05-18 19:58 ` [Bug testsuite/100658] " redi at gcc dot gnu.org
2021-05-19 13:25 ` marxin at gcc dot gnu.org [this message]
2021-05-19 13:26 ` cvs-commit at gcc dot gnu.org
2021-05-19 20:51 ` gscfq@t-online.de
2021-05-21  9:13 ` marxin at gcc dot gnu.org
2021-09-17  6:35 ` pinskia 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-100658-4-v4uQjpS9lv@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: 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).