From: Joseph Myers <joseph@codesourcery.com>
To: Richard Sandiford <richard.sandiford@arm.com>
Cc: <gcc-patches@gcc.gnu.org>, <dodji@redhat.com>,
<dmalcolm@redhat.com>, <polacek@redhat.com>
Subject: Re: [C] Improve diagnostics for vector types
Date: Mon, 30 Sep 2019 21:42:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1909302141510.1462@digraph.polyomino.org.uk> (raw)
In-Reply-To: <mpt36ge9bo4.fsf@arm.com>
On Mon, 30 Sep 2019, Richard Sandiford wrote:
> 2019-09-30 Richard Sandiford <richard.sandiford@arm.com>
>
> gcc/c-family/
> * c-pretty-print.c (pp_c_specifier_qualifier_list): If a vector type
> has a type name, use it in preference to the __vector syntax.
>
> gcc/testsuite/
> * gcc.dg/diag-aka-3.c: New test.
> * gcc.target/aarch64/diag_aka_1.c: New test.
> * g++.dg/diagnostic/aka4.C: New test.
OK.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2019-09-30 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 13:05 Richard Sandiford
2019-09-30 21:42 ` Joseph Myers [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=alpine.DEB.2.21.1909302141510.1462@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dmalcolm@redhat.com \
--cc=dodji@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=polacek@redhat.com \
--cc=richard.sandiford@arm.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).