From: Jeff Law <law@redhat.com>
To: luoxhu@linux.ibm.com, gcc-patches@gcc.gnu.org
Cc: segher@kernel.crashing.org, wschmidt@linux.ibm.com,
joseph@codesourcery.com, polacek@redhat.com,
Xiong Hu Luo <luoxhu@linux.vnet.ibm.com>
Subject: Re: [PATCH] PR c/43673 - Incorrect warning in dfp printf.
Date: Fri, 31 May 2019 19:16:00 -0000 [thread overview]
Message-ID: <14bde2c8-c606-8750-2c7c-fb8a180309c1@redhat.com> (raw)
In-Reply-To: <1551143599-26436-1-git-send-email-luoxhu@linux.ibm.com>
On 2/25/19 6:13 PM, luoxhu@linux.ibm.com wrote:
> From: Xiong Hu Luo <luoxhu@linux.vnet.ibm.com>
>
> dfp printf/scanf of Ha/HA, Da/DA and DDa/DDA is not set properly, cause
> incorrect warning happens:
> "use of 'D' length modifier with 'a' type character".
>
> Regression-tested on powerpc64le-linux, OK for trunk and gcc-8?
>
> gcc/c-family/ChangeLog:
>
> 2019-02-25 Xiong Hu Luo <luoxhu@linux.ibm.com>
>
> PR c/43673
> * c-format.c (print_char_table, scanf_char_table): Replace BADLEN with
> TEX_D32, TEX_D64 or TEX_D128.
>
> gcc/testsuit/ChangeLog:
>
> 2019-02-25 Xiong Hu Luo <luoxhu@linux.ibm.com>
>
> PR c/43673
> * gcc.dg/format-dfp-printf-1.c: New test.
> * gcc.dg/format-dfp-scanf-1.c: Likewise.
THanks. Installed on the trunk.
Sorry for the delays and miscommunications.
jeff
prev parent reply other threads:[~2019-05-31 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 2:16 luoxhu
2019-03-04 1:13 ` *Ping* " Xiong Hu Luo
2019-05-21 0:56 ` luoxhu
2019-05-21 15:53 ` Jeff Law
2019-05-23 22:26 ` Joseph Myers
2019-05-31 18:46 ` Jeff Law
2019-05-31 19:16 ` Jeff Law [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=14bde2c8-c606-8750-2c7c-fb8a180309c1@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=luoxhu@linux.ibm.com \
--cc=luoxhu@linux.vnet.ibm.com \
--cc=polacek@redhat.com \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.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).