From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org, Phil Muldoon <pmuldoon@redhat.com>
Subject: Re: [obv] compile-print.exp: xfail->kfail for '@' GDB array operator
Date: Fri, 05 Jun 2015 13:24:00 -0000 [thread overview]
Message-ID: <20150605132452.GA3376@host1.jankratochvil.net> (raw)
In-Reply-To: <86d21ao5vw.fsf@gmail.com>
On Fri, 05 Jun 2015 11:34:43 +0200, Yao Qi wrote:
> If '@' is rejected in GCC,
BTW '@' was implemented in the GCC patch only under condition of being run by
GDB/libcc1.
> '@' isn't a valid operator for C language,
So even if the GCC patch was accepted '@' still would not be a valid operator
for C language; that is correct.
Jan
prev parent reply other threads:[~2015-06-05 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 19:38 Jan Kratochvil
2015-06-05 9:35 ` Yao Qi
2015-06-05 12:40 ` Jan Kratochvil
2015-06-05 15:19 ` Doug Evans
2015-06-05 15:26 ` Jan Kratochvil
2015-06-05 16:13 ` Yao Qi
2015-06-05 21:23 ` Jan Kratochvil
2015-06-05 13:24 ` Jan Kratochvil [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=20150605132452.GA3376@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.com \
--cc=qiyaoltc@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