public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: naoki ueda <tantan19tanuki@gmail.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: About ' * ' not recognized
Date: Sat, 21 Jan 2023 10:18:12 +0900 [thread overview]
Message-ID: <CAMJE2na2m+b5fGKmWk4FFyLcA4DzkGQTcBqz-O=33VQD8A1kXA@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1m=E81QdW-zuY-LJ0omjM5K-54b85UwrqaE5Gw6q=_ckg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
Ok, I see.
2023年1月21日(土) 10:12 Andrew Pinski <pinskia@gmail.com>:
> On Fri, Jan 20, 2023 at 5:05 PM naoki ueda via Gcc-bugs
> <gcc-bugs@gcc.gnu.org> wrote:
> >
> > When I tried to execute the attached file mycalc.c with a command line
> > argument, it could not be executed normally only in the case of '*'.
> > '+', '-' and '/' can be executed normally, but the compiler cannot
> > execute '*' normally. Isn't this a gcc bug?
>
> First off this email list is really for automated messages from gcc's
> bugzilla rather than from users reporting issues.
>
> >
> >
> > ~/Clearning$ ./mycalc 20 * 30
>
> Oh * here is being handled by the shell you are using and being
> expanded as all the files in the current working directory. This has
> nothing to do with GCC really.
> You can use quotes around the * to force the shell not expanding it
> such as this:
> ./mycalc 20 '*' 30
>
> or you use \ to force the shell not to expand what comes after the * like
> this:
> ./mycalc 20 \* 30
>
> Thanks,
> Andrew Pinski
>
> > 用法:mycalc 数値1 演算子 数値2
>
prev parent reply other threads:[~2023-01-21 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 1:04 naoki ueda
2023-01-21 1:12 ` Andrew Pinski
2023-01-21 1:18 ` naoki ueda [this message]
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='CAMJE2na2m+b5fGKmWk4FFyLcA4DzkGQTcBqz-O=33VQD8A1kXA@mail.gmail.com' \
--to=tantan19tanuki@gmail.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=pinskia@gmail.com \
/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).